record:
1. Re execute – & gt; Phenomenally, it is found that the target app is not opened on the mobile phone, and the same error is always reported
Original error: the instrumentation process cannot be initialized
2. The error report includes: at uiautomator2server.startsession. It is preliminarily suspected that it is io.appium.uiautomator2.server app
Check that skipserverinstallation: true
in config is changed to skipserverinstallation: false
3. Execute it again and it is successful ✅
4. Then change skipserverinstallation: true
(in this way, io.appium.uiautomator2.server will not be installed again next time)
Root cause:
io.appium.uiautomator2.server is not installed on the new device,
and skipserverinstallation in the local configuration: true,
– & gt
in this way, the installation of io.appium.uiautomator2.server will be skipped,
resulting in the failure of the new device to start the server normally
reference resources: https://blog.csdn.net/YUICUI/article/details/112468679
Similar Posts:
- App Automated execution error: UiAutomationService android.accessibilityservice.IAccessibilityServiceClient$Stub$Proxy@63c31ebalready registered!
- [Solved] Stderr: ‘Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION: Failed to parse…
- [Solved] Appium Error: selenium.common.exceptions.WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: Can’t stop process; it’s not currently runni…
- [Solved] appium Error: Message: Cannot set the element to ‘XXXX’. Did you interact with the correct element?
- Kali Linux 2.0 U disk installation error, unable to load CD-ROM
- [Solved] Errors reported by genymotion, UI autoviewer and appium
- RuntimeError: cuda runtime error (30) : unknown errorr
- Redis service failed to start, prompt: redis server: command not found
- [Solved] appium Error: A new session could not be created
- Appium – multiprocessing.pool.MaybeEncodingError-[“Can’t pickle local object ‘PoolManager.__init…