Device has no activity for more than 100 seconds - during the testSee original GitHub issue
Hi. I’m getting a message in the Appium logs while testing is in progress:
Found Device with udid Samsung-Galaxy-S10-Android-12:5555 has no activity for more than 100 seconds
even though the test is still running. When no test is queued then there is no problem, the test is completed. However, when someone else tries to use the device it hits a busy error.
UiAutomator2 Server cannot start because the local port #46223 is busy. Make sure the port you provide via 'systemPort' capability is not occupied. This situation might often be a result of an inaccurate sessions management, e.g. old automation sessions on the same device must always be closed before starting new ones.
Do you know where the problem might be?
Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy Appium: v2.0.0-beta.44 Device-farm: v2.0.0-beta.4 Device: Emulator on docker https://github.com/budtmo/docker-android connected remote to adb
- Created a year ago
- Comments:11 (7 by maintainers)
Top GitHub Comments
AFAIK, this might occur when the session is not deleted and a new session is being created on the same device.
@yusufperferfer Could you share the test details… if possible set a sample repo. That would help us debug the issue faster.
It’s just that the tests on the session are ongoing, and despite their duration, the device farm reports the device as not in use, even though it is not. It seems to me that this is not an issue of deleting the session, as it should not be deleted while the test is in progress