-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled Exception: Patrol action failed: NativeAutomatorClientException: initialize() failed with Invalid response: 500 java.lang.RuntimeException: Error while connecting UiAutomation@977cd79[id=-1, displayId=0, flags=0] #2448
Comments
Hi @mk-fk , there should not be a need to turn on accessibility. Is there more of this logs? More stack trace? |
|
These are the logs I got from logcat. |
I've executed the test in Firebase TestLab physical device |
@jBorkowska any updates on this ? Did you get a chance to look into the logs ? |
Sorry for late response. I did look at this but I haven't found anything. Maybe it's because package name, in logs you have myapp.com, is this your real package name? |
|
@mk-fk are you able to reproduce this on newest patrol (3.14.0) and patrol_cli (3.5.0)? Because based on our latest knowledge this should work now |
Steps to reproduce
I'm using patrol 2.3.2. Patrol cli: 2.2.2.
I can able to run in emulator API 33.
Samsung A54 API 34 One UI 6.1.
But this error shows on Samsung Tab s9 FE API 34 One UI 6.
Is it related to accessibility or any settings need to be turned on in my tablet ?
Actual results
App opens for a second and closed.
Logs
Logs
Patrol version
I'm using patrol 2.3.2. Patrol cli: 2.2.2.
Patrol Doctor output
Patrol Doctor output
Flutter Doctor output
Flutter Doctor output
The text was updated successfully, but these errors were encountered: