Open alyssaw90 opened 1 year ago
What do you get in the logs from the device? The message AppWillTerminateWithError
means a native crash or an unhandled JS error.
@noomorph - When I check the pipeline for logs, no logs can be found. My team and I think it is because logs aren't being created. We have also confirmed we are calling the correct flags to create logs. I am going to check again today to see if the logs may have been missed.
@d4vidi do we (technically) support React Native 0.65.x ? I guess we do, right? Maybe 0.59 is an issue, but 60+ is ok, AFAIR.
@alyssaw90 if there's indeed nothing literally, well, you could tweak your ci script to run this log dumper in parallel:
/usr/bin/xcrun simctl spawn booted log stream --level debug --style compact --predicate 'process == "mymicrosoft"' &
and see what it prints when you get AppWillTerminateWithError.
We don't check that far back for regressions so I can't give a hard yes on RN .65. I wouldn't be surprised to learn that it's not fully functional.
Related idea: #3854.
Thank you @noomorph and @d4vidi for this additional information. I was able to find some logs and going through them this week.
@alyssaw90 were you able to resolve the issue. I've noticed unless the react package manager is running the tests timeout. I am able to replicate it locally, have the package manager running and tests pass.
We have not been able to resolve the issue. I will pass this on that the timeout could be an issue and test that in our pipeline.
It's unclear for me now what to do about this issue š¤
Also having a similar issue with android. It seems like there is an issue with the launchApp() wrapper that makes it time out
Bump, spent literally weeks with Bitrise support trying to fix this and it's definitely a Detox issue. I also have the same issue where the logs don't get created.
This is a total blocker, would appreciate just a response from the Detox team about this!
I am 90% sure its something with the timeout in launchApp().
Here's a trace level log dump
It seems like the issue may relate to some kind of 45000 ms timeout in the code.
I see this in node_modules/detox/src/devices/common/drivers/android/exec/ADB.js:
const INSTALL_TIMEOUT = 45000; // TODO Double check 45s makes sense
So it seems like there was some debate about whether this is right.
I used patch-package to change this to 300000 and it still times out, claiming the 45000 timeout!!
The patch:
@owens-ben & @alyssaw90. I've previously had some similar issues with a different provider. Wrapping the launch app command in a retry util seemed to help, but might not in your case.
@noomorph Any solution for this issue?
@owens-ben did you get unblocked now?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe the issue is still relevant, please test on the latest Detox and report back.
Thank you for your contributions!
For more information on bots in this repository, read this discussion.
The issue has been closed for inactivity.
Still an issue.
Could you share device logs and video recording from your device? Just to make sure, the app runs locally on emulators well enough, right?
@noomorph yes, it works on android emulators as well as iOS emulators (including in bitrise).
There essentially are no logs beyond what's been shared. And we can't share a video as the Linux machines do not support vnc.
Hey @owens-ben , I also encountered this issue and it took me much time, finally I found it's because of the adb communication is very slow, which caused the apk can't be installed on the emulator. I executed the following commands to restart the adb server and the issue went away.
adb kill-server
adb start-server
Maybe it's also appropriate for your and other's situation. Good luck. :)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe the issue is still relevant, please test on the latest Detox and report back.
Thank you for your contributions!
For more information on bots in this repository, read this discussion.
Description
When running our detox tests locally everything is working as expected. When running the detox test via the Azure pipeline we get a timeout error (see below). The pipeline has worked in the past, but it is now broken. We have used the troubleshooting guidelines but could use some recommendations on what the issue could be. Is it because of the React Native version we are using? Do we need to upgrade our detox version? What versions of React Native does detox support?
Your environment
Detox version: 19.13.0 React Native version: 0.65.1 Node version: 14.21.2 (pipeline) 16.17.1 (laptop) Device model: Azure Pipelines/Mac OS: Mac OS 12.6.2(pipeline)/12.6.2(laptop) Test-runner (select one): Other