timeout of adb command / wait parameter
See original GitHub issueThe problem
My goal is to run end-to-end tests with Appium on an App built with Expo (turtle-cli). When starting the session, the app launches on the smartphone, but appium throws a timeout error:
[MJSONWP] Encountered internal error running command: Error: Cannot start the 'com.example.testetoeapplauda' application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Error executing adbExec. Original error: 'Command 'adb -P 5037 -s ENU7N15B03007818 shell am start -W -n com.example.testetoeapplauda/host.exp.exponent.MainActivity -S' timed out after 20000ms'. Try to increase the 20000ms adb execution timeout represented by 'adbExecTimeout' capability
The interesting part is the adb shell command. When I run this command manually, the app launches, but the command does not finish - it just hangs forever.
When I remove the parameter -W it is not blocking.
So, how can I change Appium to don’t use the -W flag on the adb command?
Environment
- Real device or emulator/simulator: real device Android 8.1.0
- Appium CLI or Appium.app|exe: Appium-Desktop 1.13.0
Code To Reproduce Issue [ Good To Have ]
Here is a link to the APK file to reproduce the problem: expo-app-test apk file
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (5 by maintainers)
@jjoe64 From the next version,
appWaitForLaunch: false
will allow avoiding -W optionThanks
yeah that’s working, thanks!