Error: The instrumentation process cannot be initialized. Make sure the application under test is doesnot crash.Investigate logcat output

Vishala_Nagaraj · January 18, 2023, 9:57am

What does the above error mean? Started getting it all of a sudden and unable to launch appium session.

Any help greatly appreciated as this is blocking our project

wreed · January 18, 2023, 4:51pm

Sometimes it means there is a pop up on the screen that is blocking Appium. Hard to say without a log, which you could share as a git gist:

https://docs.github.com/en/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists

Vishala_Nagaraj · January 19, 2023, 6:45am

My github account has some authentication issue.Please find the logs in below link:

https://drive.google.com/file/d/10vvLxWOzEmF9XCD8MNyt5wDiIcSbMTi_/view?usp=sharing

appium.txt is server logs and instrumentation.txt is logcat logs

I researched on net and none of solutions worked.

Tried uninstalling uiautomator2 apks and it did not work.

Switching to uiautomator1 worked.But i do not want to go for it as it is not right approach as uiautomator1 is deprecated.

Please help.Thanks in advance for you time !

wreed · January 19, 2023, 5:18pm

This is the error I’m seeing:

java.lang.IllegalStateException: UiAutomationService android.accessibilityservice.IAccessibilityServiceClient$Stub$Proxy@59896baalready registered!

I found a document on killing the service that is already registered here:

https://debugah.com/app-automated-execution-error-uiautomationservice-android-accessibilityservice-iaccessibilityserviceclientstubproxy63c31ebalready-registered-20050/

One thing that seems peculiar about your setup is that there appear to be 5 devices connected to the computer:

[debug] [ADB] Connected devices: [{“udid”:“R3CM603JHVW”,“state”:“device”},{“udid”:“R3CN30YD8FP”,“state”:“device”},{“udid”:“R3CNB0FPA4N”,“state”:“device”},{“udid”:“R3CNC0EZPVH”,“state”:“device”},{“udid”:“R3CR315S5TV”,“state”:“device”}]

If you only connect one device does this problem go away? This seems like info you should have shared…

Finally, there is a bug filed:

github.com/appium/appium

java.lang.IllegalStateException: UiAutomationService android.accessibilityservice.IAccessibilityServiceClient$Stub$Proxy@2c7a0c0already registered!

opened 04:16AM - 27 Jan 22 UTC

closed 02:02PM - 29 Jan 22 UTC

youngfreeFJS

ThirdParty UIAutomator2

## The problem can not create session because android.accessibilityservice.IAcc…essibilityServiceClient already registered ## Environment * Appium version (or git revision) that exhibits the issue: v1.22.2 * Last Appium version that did not exhibit the issue (if applicable): is v1.x latest version * Desktop OS/version used to run Appium: OSX 10.15 * Node.js version (unless using Appium.app|exe): v12.18.3 * Npm or Yarn package manager: npm * Mobile platform/version under test: Android emulator 9 * Real device or emulator/simulator: emulator * Appium CLI or Appium.app|exe: CLI ## Details each test case use a new create appium server, and use udid bind android emulator(not reboot), we will delete session and release server every case. But after running 8-10 test case， this problem will happens and since then the test case on this emulator will all failed with this issue. Whether the service was not deleted in the previous case? ## Link to Appium logs 1. create session error log here: https://gist.github.com/youngfreeFJS/c5c8f04da7561570b95479d60ac67ccf 2. the previous one of this error case log (use same emualor ): https://gist.github.com/youngfreeFJS/c3700ecedceb54f25f8fb11f883e689c ## Code To Reproduce Issue [ Good To Have ] Please remember that with sample code it's easier to reproduce the bug and it's much faster to fix it. Please git clone https://github.com/appium/appium and from the `sample-code` directory, use one of your favourite languages and sample apps to reproduce the issue. In case a similar scenario is missing in sample-code, please submit a PR with one of the sample apps provided.