-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
detox verb instrumentationProcess terminated due to receipt of signal null #764
Comments
I get the exact same thing (trying to run on android emulator). The react native example project works fine on my mac, and I have gone to great lengths to match versions etc (I am at 0.51.1, detox 7.3.7, node 8.9.3). My error looks like:
The installed app seems to work, if I start it after I exit out of the detox test run. The only thing that I consider relevant in logcat is:
|
Anyone Can help on this ? I am stuck with this issue |
if there are any other logs, I need to provide, let me know! |
ADB logcat would probably have the needed data to understand your issue. Seems like the app crashes |
@rotemmiz ok will try to get that. Also the app seems to work, as I mentioned, if i just started it by tapping on it on the emulator (the app that got installed as part of detox test -c android.emu.debug). Let me add this. When my app starts, the 'landing' screen is native (Android java) NOT an RN component. The launch of the RN component is on tap in from there. In iOS, it does not seem to matter as inside our Detox test, we grab the button to tap from the landing screen, simulate the tap (still inside the test), and then the RN component gets launched. Does that make a difference on Android? |
Not sure I understand what "we grab the button to tap from the launch script, simulate the tap (still inside the test)" is, but having a hybrid app that initiates RN only at a later stage may cause sync issues on Android (pretty sure we already tackled that on iOS). |
I will try to get some time to generate a repo that produces this error. Sorry, I don't know why I typed 'launch script' :-) I edited the post. So we pretty much do a:
LaunchReactNativeComponent is a native button (does not come from RN) and in iOS, at least, we set its accessibility id to 'LaunchReactNativeComponent' so we can reference it inside the detox test. I hope this helps! |
I still don't understand the issue. Does the app crash on tap? |
This issue is no longer exist from my side , I am closing down this issue |
@yogeshthanvi how did you fix it? |
@rotemmiz, I got logcat info for you: detox log looks like this:
corresponding logcat right around the crash is:
|
Are you running the correct Android flavour ? RN45 needs |
We use the issue tracker exclusively for bug reports and feature requests. This issue appears to be a general usage or support question. Instead, please ask a question on Stack Overflow with the |
I have this:
in my app build file |
and when I do a detox build, I see this:
FYI |
I'm not sure what's the issue then, we moved past RN 45 a long time ago. If it's possible, try upgrading RN on your project and see if the error persists. |
I am on 0.55... |
Do I need to be on a specific Android SDK for the emulator that I point detox to? |
No hard dependency, but try API lvl 27 |
got it working! API lvl 27 was the culprit! |
What did you use before? |
26 |
my project is set to to 27 btw:
|
oh I also changed to:
|
So was it configured with the right flavour ? |
I am facing an issue as mentioned in subject for Android . I am executing the test cases on Android device following are the details
Android version : 7.0
react-native-cli: 2.0.1
react-native: 0.45.1
The text was updated successfully, but these errors were encountered: