After noticing I was posting my issue in a similar but not same topic I prefer to create a new one.
I have a workspace with different test suite pipelines and from time to time randomly one or more of the TCs failed due to the same error.
Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Cannot start the 'com.nemergent.client.mcptt' application. Consider checking the driver's troubleshooting documentation. Original error: Error executing adbExec. Original error: 'Command '/opt/android-sdk/platform-tools/adb -P 5037 -s A75359FRCN94HDV01CC shell am start -W -n com.android.project/com.android.project.MainScreen-S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000' timed out after 20000ms'. Try to increase the 20000ms adb execution timeout represented by 'adbExecTimeout' capability
Before asking it. All the TC have the exact same configuration and environment. The devices are always the same and never fail the same TCs.
For more Appium info check the appium log attached here
appiumServerLogs.log (276.7 KB)
First, I agree that this is a different issue and thanks for opening a
new topic, which is appropriate.
Second, here is the troubleshooting documentation for uiautomator2 driver:
Third, I think you forgot to attach the log. I will go over when you attach.
I have updated the post with the Appium log
Ok, I see the error. There are a couple of recommendations in the error, have you done these?
- Consider checking the driver’s troubleshooting documentation.
- Try to increase the 20000ms adb execution timeout represented by ‘adbExecTimeout’ capability
I have provided a link above to the driver’s troubleshooting documentation. Here is a link to adbExecTimeout documentation:
Please follow the troubleshooting documentation and set the adbExecTimeout setting and report back the results.
I have increased the adbExecTimeout to 30000ms and even with that I have the same issue. Check the Appium log below.
appiumServerLogs.log (171.9 KB)
Ok, you’ll have to go through the troubleshooting documentation, make changes and report back.
After a long time trying different configuration and going through the troubleshooting documentation I have been unable to solve this problem. As far as I have found could it be related to the app itself? I mean I know for sure that at the time the app is launched tries to bind with an SDK. Could the hogging error be related to it?
I mean what I see on the device at the time this issue happens is that the it gets stuck on the app launch screen. The white one with the app logo in the middle of the screen. Maybe the bind of the app with the SDK is the one making the device to get stuck?
Apart of this another thing that I think it could affect is that during all the TC I have an screen record command setted on the background