Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Device has no activity for more than 100 seconds - during the test
See original GitHub issueHi. 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
Issue Analytics
- State:
- Created a year ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@yusufperferfer @SubbuLomada Please try the latest version. Issue fixed.
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