wix
Detox can't seem to connect to the test app(s)!
Did you test using the latest Detox?
- [x] I have tested this issue on the latest Detox release and it still reproduces.
Did your test fail and you're not sure why?
- [x] I have read the troubleshooting guide and it didn't help me.
What happened?
I saw all the issues here but anyone help with this problem however can't be fixed my problem. I can run on iOS platform, but in Android I can't, and I'm in this problem for many days. Can anyone help me with this, please?
15:12:16.847 detox[54729] B jest --config e2e/jest.config.js 15:12:28.286 detox[54730] i starter.test.js is assigned to AttachedDevice:ZE223HGBVK 15:12:32.122 detox[54730] i An error occurred while waiting for the app to become ready. Waiting for disconnection... error: Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process. 15:12:32.123 detox[54730] i The app disconnected. 15:12:32.128 detox[54730] i Splash: should have splash screen 15:12:32.131 detox[54730] i Splash: should have splash screen [FAIL]
15:12:32.144 detox[54730] i Detox can't seem to connect to the test app(s)!
HINT:
The test app might have crashed prematurely, or has had trouble setting up the connection. Refer to our troubleshooting guide, for full details: https://wix.github.io/Detox/docs/troubleshooting/running-tests#tests-execution-hangs
FAIL e2e/starter.test.js (14.871 s) Splash ✕ should have splash screen (3 ms)
● Splash › should have splash screen
Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process.
1 | describe('Splash', () => {
2 | beforeAll(async () => {
> 3 | await device.launchApp();
| ^
4 | });
5 |
6 | beforeEach(async () => {
at Object.launchApp (e2e/starter.test.js:3:18)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
at Object.<anonymous> (node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)
15:12:39.342 detox[54730] i FirstPage.test.js is assigned to AttachedDevice:ZE223HGBVK 15:12:41.927 detox[54730] i An error occurred while waiting for the app to become ready. Waiting for disconnection... error: Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process. 15:12:41.928 detox[54730] i The app disconnected. 15:12:41.932 detox[54730] i FirstPage: should have first screen 15:12:41.933 detox[54730] i FirstPage: should have first screen [FAIL] 15:12:41.934 detox[54730] i FirstPage: should be tap on button first time 15:12:41.935 detox[54730] i FirstPage: should be tap on button first time [FAIL] 15:12:41.937 detox[54730] i FirstPage: should be tap on button Already client 15:12:41.937 detox[54730] i FirstPage: should be tap on button Already client [FAIL]
15:12:41.953 detox[54730] i Detox can't seem to connect to the test app(s)!
HINT:
The test app might have crashed prematurely, or has had trouble setting up the connection. Refer to our troubleshooting guide, for full details: https://wix.github.io/Detox/docs/troubleshooting/running-tests#tests-execution-hangs
FAIL e2e/FirstPage.test.js (9.8 s) FirstPage ✕ should have first screen ✕ should be tap on button first time (1 ms) ✕ should be tap on button Already client
● FirstPage › should have first screen
Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process.
3 | describe('FirstPage', () => {
4 | beforeAll(async () => {
> 5 | await device.launchApp();
| ^
6 | });
7 |
8 | beforeEach(async () => {
at Object.launchApp (e2e/FirstPage.test.js:5:18)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
at Object.<anonymous> (node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)
● FirstPage › should be tap on button first time
Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process.
3 | describe('FirstPage', () => {
4 | beforeAll(async () => {
> 5 | await device.launchApp();
| ^
6 | });
7 |
8 | beforeEach(async () => {
at Object.launchApp (e2e/FirstPage.test.js:5:18)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
at Object.<anonymous> (node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)
● FirstPage › should be tap on button Already client
Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process.
3 | describe('FirstPage', () => {
4 | beforeAll(async () => {
> 5 | await device.launchApp();
| ^
6 | });
7 |
8 | beforeEach(async () => {
at Object.launchApp (e2e/FirstPage.test.js:5:18)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
at Object.<anonymous> (node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)
Test Suites: 2 failed, 2 total Tests: 4 failed, 4 total Snapshots: 0 total Time: 24.722 s Ran all test suites. 15:12:42.067 detox[54729] E Command failed with exit code = 1: jest --config e2e/jest.config.js
What was the expected behaviour?
No response
Help us reproduce this issue!
No response
In what environment did this happen?
Detox version: React Native version: Has Fabric (React Native's new rendering system) enabled: (yes/no) Node version: Device model: Android version: Test-runner (select one): jest / other
Detox logs
Detox logs
paste logs here!
Device logs
Device logs
paste your device.log here!
More data, please!
No response
Thanks @vauruk for reporting this issue. I am also getting exactly the same issue. Any update?
No, @uasghar-smile I haven't found an answer, and I've looked into all the look problems, but I can't fix this.
Not really! Still stuck with this issue.
From: nvacheishvili @.> Sent: Saturday, 19 April 2025 12:09 AM To: wix/Detox @.> Cc: Usama Asghar @.>; Mention @.> Subject: Re: [wix/Detox] Detox can't seem to connect to the test app(s)! (Issue #4753)
Same issue here any update?
— Reply to this email directly, view it on GitHubhttps://github.com/wix/Detox/issues/4753#issuecomment-2816043631, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYQGHVCPBR64XTL26W7RBWD22FEXJAVCNFSM6AAAAAB2TZSR2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJWGA2DGNRTGE. You are receiving this because you were mentioned.Message ID: @.***>
[https://avatars.githubusercontent.com/u/15612632?s=20&v=4]nvacheishvili left a comment (wix/Detox#4753)https://github.com/wix/Detox/issues/4753#issuecomment-2816043631
Same issue here any update?
— Reply to this email directly, view it on GitHubhttps://github.com/wix/Detox/issues/4753#issuecomment-2816043631, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYQGHVCPBR64XTL26W7RBWD22FEXJAVCNFSM6AAAAAB2TZSR2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJWGA2DGNRTGE. You are receiving this because you were mentioned.Message ID: @.***>
Thanks @vauruk for reporting this issue. I am also getting exactly the same issue. Any update?
No, I have not received any update and have not found another fix to this problem.
@vauruk Are you using react-native-mmkv in your project?
In my case this was caused by app crash due to mmkv unable to mock the storage.
@vauruk Are you using react-native-mmkv in your project?
In my case this was caused by app crash due to mmkv unable to mock the storage.
Hi @thisara95, but I haven't this lib in my project, perhaps another lib uses this, I'm gonna see if this lib! tks for your tip.
@d4vidi sir , @gosha212 sir , i'm also getting same issue - kindly provide the fix for this.
Thanks
@vauruk @manojmehra-spraxa can you please share the device logs, the platform and the version of react native? Can you share a sample project with the problem?
@gosha212 kindly have a look into this error details and please provide update
`23:48:34.807 detox[14916] i An error occurred while waiting for the app to become ready. Waiting for disconnection... error: The pending request #-1000 ("isReady") has been rejected due to the following error:
The app has unexpectedly disconnected from Detox server. 23:48:34.809 detox[14916] i The app disconnected. 23:48:34.812 detox[14916] i App failed to launch: The pending request #-1000 ("isReady") has been rejected due to the following error:
The app has unexpectedly disconnected from Detox server.
at createErrorWithUserStack (D:\CoolR-RN-Upgrade\CoolR-BLE-Hybrid\CoolR_ReactNative\node_modules\detox\src\utils\errorUtils.js:36:27)
at RuntimeDevice.stackTraceWrapper [as launchApp] (D:\CoolR-RN-Upgrade\CoolR-BLE-Hybrid\CoolR_ReactNative\node_modules\detox\src\utils\wrapWithStackTraceCutter.js:9:34)
at Object.launchApp (D:\CoolR-RN-Upgrade\CoolR-BLE-Hybrid\CoolR_ReactNative\e2e\starter.test.js:6:20)
at Generator.next (
at jestAdapter (D:\CoolR-RN-Upgrade\CoolR-BLE-Hybrid\CoolR_ReactNative\node_modules\jest-circus\build\legacy-code-todo-rewrite\jestAdapter.js:79:19)
at runTestInternal (D:\CoolR-RN-Upgrade\CoolR-BLE-Hybrid\CoolR_ReactNative\node_modules\jest-runner\build\runTest.js:367:16)
at runTest (D:\CoolR-RN-Upgrade\CoolR-BLE-Hybrid\CoolR_ReactNative\node_modules\jest-runner\build\runTest.js:444:34) {
name: 'DetoxRuntimeError'
}
23:48:34.816 detox[14916] i Login Flow: should login successfully with valid credentials
23:48:34.831 detox[14916] i Detox can't seem to connect to the test app(s)!
HINT:
Have you forgotten to call 'device.launchApp()' in the beginning of your test? Refer to our troubleshooting guide, for full details: https://wix.github.io/Detox/docs/troubleshooting/running-tests#tests-execution-hangs
The following package could not be delivered:
{ type: 'invoke', params: [Object], messageId: 1 } 23:48:34.835 detox[14916] i Login Flow: should login successfully with valid credentials [FAIL]
FAIL e2e/starter.test.js (34.595 s)
Login Flow
× should login successfully with valid credentials (18 ms)
● Login Flow › should login successfully with valid credentials
Detox can't seem to connect to the test app(s)!
HINT:
Have you forgotten to call 'device.launchApp()' in the beginning of your test?
Refer to our troubleshooting guide, for full details: https://wix.github.io/Detox/docs/troubleshooting/running-tests#tests-execution-hangs
---
The following package could not be delivered:
{
type: 'invoke',
params: [Object],
messageId: 1
}
15 | await waitFor(element(by.id('login-screen')))
16 | .toBeVisible()
> 17 | .withTimeout(5000);
| ^
18 |
19 |
20 | });
at createErrorWithUserStack (node_modules/detox/src/utils/errorUtils.js:36:27)
at Client._doSendAction (node_modules/detox/src/client/Client.js:168:32)
at Client._sendMonitoredAction (node_modules/detox/src/client/Client.js:161:25)
at Client.sendAction (node_modules/detox/src/client/Client.js:147:14)
at Client.execute (node_modules/detox/src/client/Client.js:132:25)
at InvocationManager.execute (node_modules/detox/src/invoke.js:11:39)
at WaitForInteraction.execute (node_modules/detox/src/android/interactions/native.js:23:31)
at WaitForInteraction.withTimeout (node_modules/detox/src/android/interactions/native.js:59:16)
at Object.withTimeout (e2e/starter.test.js:17:8)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
at Object.<anonymous> (node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)
Test Suites: 1 failed, 1 total
Tests: 1 failed, 1 total
Snapshots: 0 total
Time: 34.722 s
Ran all test suites.
23:48:35.022 detox[7224] E Command failed with exit code = 1:
jest --config e2e/jest.config.js `
react-native : v0.76.0 platform : android
@manojmehra-spraxa Can you please enable the full logs as suggested https://wix.github.io/Detox/docs/troubleshooting/running-tests/#if-you-dont-see-your-app-running-on-the-device? Can you see what crashes the app?
@manojmehra-spraxa Can you please enable the full logs as suggested https://wix.github.io/Detox/docs/troubleshooting/running-tests/#if-you-dont-see-your-app-running-on-the-device? Can you see what crashes the app?
package.json
{ "name": "DriveHelpApp", "version": "0.0.1", "private": true, "scripts": { "android": "react-native run-android", "ios": "react-native run-ios", "lint": "eslint .", "start": "react-native start", "clean": "watchman watch-del-all && rm -rf node_modules && yarn && yarn start --reset-cache && rm -rf /tmp/metro-*", "e2e-ios": "detox build --configuration ios.sim.debug && detox test --configuration ios.sim.debug", "e2e-android": "detox build --configuration android.emu.debug && detox test --configuration android.emu.debug", "test": "jest" }, "dependencies": { "@react-navigation/elements": "^2.3.1", "@react-navigation/material-bottom-tabs": "^6.2.29", "@react-navigation/material-top-tabs": "^7.2.3", "@react-navigation/native": "^7.0.19", "@react-navigation/native-stack": "^7.3.3", "@react-navigation/stack": "^7.2.3", "@reduxjs/toolkit": "^2.6.1", "@rneui/base": "^4.0.0-rc.8", "@rneui/themed": "^4.0.0-rc.8", "axios": "^1.8.4", "crypto-js": "^4.2.0", "i18n-js": "^4.5.1", "lottie-react-native": "^7.2.2", "moment-timezone": "^0.5.48", "react": "19.0.0", "react-native": "0.78.1", "react-native-config": "^1.5.5", "react-native-gesture-handler": "^2.24.0", "react-native-paper": "^5.13.1", "react-native-safe-area-context": "^5.3.0", "react-native-screens": "^4.9.2", "react-native-svg": "^15.11.2", "react-native-vector-icons": "^10.2.0", "react-redux": "^9.2.0" }, "devDependencies": { "@babel/core": "^7.25.2", "@babel/preset-env": "^7.25.3", "@babel/runtime": "^7.25.0", "@react-native-community/cli": "15.0.1", "@react-native-community/cli-platform-android": "15.0.1", "@react-native-community/cli-platform-ios": "15.0.1", "@react-native/babel-preset": "0.78.1", "@react-native/eslint-config": "0.78.1", "@react-native/metro-config": "0.78.1", "@react-native/typescript-config": "0.78.1", "@types/jest": "^29.5.13", "@types/react": "^19.0.0", "@types/react-test-renderer": "^19.0.0", "detox": "^20.36.2", "eslint": "^8.19.0", "jest": "^29", "prettier": "2.8.8", "react-test-renderer": "19.0.0", "typescript": "5.0.4" }, "engines": { "node": ">=18" } }
----------------- LOGS ---------------------------------
yarn e2e-android --verbose 1 ↵ yarn run v1.22.22 $ detox build --configuration android.emu.debug && detox test --configuration android.emu.debug --verbose cd android && ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug
[Incubating] Problems report is available at: file:///Users/vandersonvauruk/Documents/workspace/vauruk/DriveHelp/DriveHelpApp/android/build/reports/problems/problems-report.html
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.12/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD SUCCESSFUL in 2s
524 actionable tasks: 24 executed, 500 up-to-date
11:54:57.976 detox[37494] B jest --config e2e/jest.config.js --verbose
watchman warning: Recrawled this watch 3 times, most recently because:
MustScanSubDirs UserDroppedTo resolve, please review the information on
https://facebook.github.io/watchman/docs/troubleshooting.html#recrawl
To clear this warning, run:
watchman watch-del '/Users/vandersonvauruk/Documents/workspace/vauruk/DriveHelp/DriveHelpApp' ; watchman watch-project '/Users/vandersonvauruk/Documents/workspace/vauruk/DriveHelp/DriveHelpApp'
11:55:06.928 detox[37495] i FirstPage.test.js is assigned to emulator-16286 (Pixel_9_Pro_API_35) 11:55:10.944 detox[37495] i An error occurred while waiting for the app to become ready. Waiting for disconnection... error: Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process. 11:55:10.945 detox[37495] i The app disconnected. 11:55:10.952 detox[37495] i FirstPage: should have first screen 11:55:10.955 detox[37495] i FirstPage: should have first screen [FAIL] 11:55:10.956 detox[37495] i FirstPage: should be tap on button first time 11:55:10.956 detox[37495] i FirstPage: should be tap on button first time [FAIL] 11:55:10.957 detox[37495] i FirstPage: should be tap on button Already client 11:55:10.957 detox[37495] i FirstPage: should be tap on button Already client [FAIL]
11:55:10.977 detox[37495] i Detox can't seem to connect to the test app(s)!
HINT:
The test app might have crashed prematurely, or has had trouble setting up the connection. Refer to our troubleshooting guide, for full details: https://wix.github.io/Detox/docs/troubleshooting/running-tests#tests-execution-hangs
FAIL e2e/FirstPage.test.js (12.566 s) FirstPage ✕ should have first screen (4 ms) ✕ should be tap on button first time ✕ should be tap on button Already client
● FirstPage › should have first screen
Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process.
3 | describe('FirstPage', () => {
4 | beforeAll(async () => {
> 5 | await device.launchApp();
| ^
6 | });
7 |
8 | beforeEach(async () => {
at Object.launchApp (e2e/FirstPage.test.js:5:18)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
at Object.<anonymous> (node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)
● FirstPage › should be tap on button first time
Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process.
3 | describe('FirstPage', () => {
4 | beforeAll(async () => {
> 5 | await device.launchApp();
| ^
6 | });
7 |
8 | beforeEach(async () => {
at Object.launchApp (e2e/FirstPage.test.js:5:18)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
at Object.<anonymous> (node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)
● FirstPage › should be tap on button Already client
Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process.
3 | describe('FirstPage', () => {
4 | beforeAll(async () => {
> 5 | await device.launchApp();
| ^
6 | });
7 |
8 | beforeEach(async () => {
at Object.launchApp (e2e/FirstPage.test.js:5:18)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
at Object.<anonymous> (node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)
11:55:15.596 detox[37495] i starter.test.js is assigned to emulator-16286 (Pixel_9_Pro_API_35) 11:55:18.448 detox[37495] i An error occurred while waiting for the app to become ready. Waiting for disconnection... error: Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process. 11:55:18.448 detox[37495] i The app disconnected. 11:55:18.450 detox[37495] i Splash: should have splash screen 11:55:18.450 detox[37495] i Splash: should have splash screen [FAIL]
11:55:18.457 detox[37495] i Detox can't seem to connect to the test app(s)!
HINT:
The test app might have crashed prematurely, or has had trouble setting up the connection. Refer to our troubleshooting guide, for full details: https://wix.github.io/Detox/docs/troubleshooting/running-tests#tests-execution-hangs
FAIL e2e/starter.test.js (7.466 s) Splash ✕ should have splash screen
● Splash › should have splash screen
Failed to run application on the device
HINT: Most likely, your tests have timed out and called detox.cleanup() while it was waiting for "ready" message (over WebSocket) from the instrumentation process.
1 | describe('Splash', () => {
2 | beforeAll(async () => {
> 3 | await device.launchApp();
| ^
4 | });
5 |
6 | beforeEach(async () => {
at Object.launchApp (e2e/starter.test.js:3:18)
at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:17)
at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:17:9)
at node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:7
at Object.<anonymous> (node_modules/@babel/runtime/helpers/asyncToGenerator.js:14:12)
Test Suites: 2 failed, 2 total Tests: 4 failed, 4 total Snapshots: 0 total Time: 20.086 s Ran all test suites. 11:55:18.500 detox[37494] E Command failed with exit code = 1: jest --config e2e/jest.config.js --verbose error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@vauruk sir , Thanks for sharing this details
@gosha212 , @d4vidi sir kindly have a look what is the issue and how can we fix this this.
@manojmehra-spraxa Looks ok for me. Can you attached also the device log from artifacts folder? Each failed test case will have one.
I appear to have exactly the same issue - so here is my device.log:
Hi @GazEdBro, there is nothing related to detox in the logs. Are you sure you're sharing the correct file?
Can you enable trace logs please by addding -l trace to your test command. Did you run detox build before?
Hi @gosha212 I have re-run the detox command using this "npx detox test --configuration android e2e/minimal.e2e.js --record-logs all" which I think should be as good as the -l trace? The device log does not have and detox references, but there is a detox log and detox.trace.json which I am attaching.
Hi, it look very strange, it says that the app crashes but there's no logs. Can you try to do the following:
- clean everything and rebuild.
- Run detox build command
- Change emulator
- Porvide us with reproduction of the problem.
On Mon, Jun 16, 2025, 13:58 GazEdBro @.***> wrote:
GazEdBro left a comment (wix/Detox#4753) https://github.com/wix/Detox/issues/4753#issuecomment-2976095170
Hi @gosha212 https://github.com/gosha212 I have re-run the detox command using this "npx detox test --configuration android e2e/minimal.e2e.js --record-logs all" which I think should be as good as the -l trace? The device log does not have and detox references, but there is a detox log and detox.trace.json which I am attaching.
detox.trace.json https://github.com/user-attachments/files/20755450/detox.trace.json detox.log https://github.com/user-attachments/files/20755449/detox.log
— Reply to this email directly, view it on GitHub https://github.com/wix/Detox/issues/4753#issuecomment-2976095170, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACWGN5HY3AT7NGIFNWESRG33D2PMJAVCNFSM6AAAAAB2TZSR2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZWGA4TKMJXGA . You are receiving this because you were mentioned.Message ID: @.***>
Hi, it look very strange, it says that the app crashes but there's no logs. Can you try to do the following:
- clean everything and rebuild.
- Run detox build command
- Change emulator
- Porvide us with reproduction of the problem. …
Hi guys, I'm following up on the discussion, but I did all these things and still haven't fixed the problem. I bought an Android smartphone to test but still the same problem
Hi @gosha212 , I agree it is very strange. These outputs were the result of everything cleaned and rebuilt :(
I am not really sure how to provide a reproduction. But here is the package.json which shows the installed libraries: { "version": "1.0.0", "main": "index.ts", "scripts": { "start": "expo start", "android": "expo run:android", "ios": "expo run:ios", "web": "expo start --web", "postinstall": "patch-package", "test": "jest --config=jest.config.js", "test:passing": "jest --config=jest.config.js tests/api.test.js tests/group-validation.test.js components/tests/ThemedText-test.tsx tests/validation.test.ts", "test:e2e": "detox test --configuration android", "e2e:build:android": "EXPO_NO_DEV_CLIENT=1 npx expo prebuild -p android && detox build --configuration android", "e2e:build:ios": "EXPO_NO_DEV_CLIENT=1 npx expo prebuild -p ios && detox build --configuration ios", "e2e:test:android": "EXPO_NO_DEV_CLIENT=1 detox test --configuration android", "e2e:test:ios": "detox test --configuration ios" }, "dependencies": { "@expo/html-elements": "^0.12.5", "@expo/vector-icons": "^14.1.0", "@react-native-async-storage/async-storage": "2.1.2", "@react-navigation/bottom-tabs": "^7.3.10", "@react-navigation/native": "^7.1.6", "expo": "^53.0.0", "expo-application": "~6.1.4", "expo-asset": "~11.1.5", "expo-blur": "~14.1.5", "expo-build-properties": "~0.14.6", "expo-constants": "~17.1.6", "expo-crypto": "~14.1.5", "expo-dev-client": "~5.2.0", "expo-device": "~7.1.4", "expo-file-system": "~18.1.10", "expo-haptics": "~14.1.4", "expo-local-authentication": "~16.0.4", "expo-localization": "~16.1.5", "expo-modules-core": "~2.4.0", "expo-notifications": "~0.31.3", "expo-router": "~5.0.7", "expo-secure-store": "~14.2.3", "expo-splash-screen": "^0.28.5", "expo-status-bar": "~2.2.3", "expo-symbols": "~0.4.5", "expo-web-browser": "~14.1.6", "i18n-js": "^4.5.1", "react": "19.0.0", "react-native": "0.79.3", "react-native-draggable-flatlist": "^4.0.3", "react-native-dropdown-picker": "^5.4.6", "react-native-elements": "^3.4.3", "react-native-gesture-handler": "~2.24.0", "react-native-gradle-plugin": "^0.71.19", "react-native-markdown-display": "^7.0.2", "react-native-pell-rich-editor": "^1.9.0", "react-native-reanimated": "~3.17.4", "react-native-safe-area-context": "^5.4.1", "react-native-screens": "~4.11.1", "react-native-webview": "^13.15.0", "zod": "^3.25.57" }, "devDependencies": { "@babel/core": "^7.27.4", "@babel/preset-env": "^7.27.2", "@babel/preset-react": "^7.27.1", "@babel/preset-typescript": "^7.27.1", "@react-native-community/cli": "^18.0.0", "@testing-library/react-native": "^12.9.0", "@types/detox": "^18.1.3", "@types/jest": "^29.5.14", "@types/react": "^19.1.7", "@types/react-test-renderer": "^18.0.0", "detox": "^20.39.0", "jest": "^29.7.0", "jest-circus": "^29.7.0", "jest-expo": "^53.0.7", "patch-package": "^8.0.0", "react-test-renderer": "19.0.0", "typescript": "^5.8.3" }, "jest": { "preset": "detox" }, "private": true }
As far as I can see, the emulator is started, the app is loaded, but the app is never started - not even an attempt (I think the app does not crash, we are just seeing the result of a timeout. I have gone through the accessible code and I cannot find exactly where the start app is supposed to be sent.
@GazEdBro Just create a side project that reproduces the issue if you can. You can see from the logs that the Android Instrumentation is exiting with code 0 because of the application crash. It is hard to understand what's wrong because the device log is clean.
Hi @gosha212 I have reproduced in a "smaller" version. But I tried to zip the folder and it comes in at 2.2GB so will not upload. Are there sub elements that you could use? Basically what would make this easiest and achievable?
@manojmehra-spraxa good point. @GazEdBro you're 50% way to solve the issue. You can just create a new repository in github and share a link.
Here you go. I did the Zip (minus node_modules and android) to be as close to the complete picture as possible.
@GazEdBro I can't start the app without the android folder. You can remove the build folder inside the android and android/app. This will reduce the size of the zip. If you're using git, you can run git clean -fdx in order to clean everything not related to the repo
Hmm, not sure I am there yet - to get this to fit inside 25MB I had to remove the .cxx directory!
@GazEdBro First problem with your project is that you're running with RN 79 while detox supports up to RN 77 ( There is an open PR for RN 78).
@gosha212 I am having the same issue running RN 0.66 ( I understand it is old but cannot upgrade RN to 0.7X yet).
