question-mark
Stuck on an issue?

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.

UIAutomator2 crashes: AppiumUiAutomator2Server:INSTRUMENTATION_RESULT: shortMsg=Process crashed

See original GitHub issue

The problem

UiAutomator2 crashes when initializing a new remote driver

Environment

  • Appium version: 1.8.1
  • Desktop OS: macOS High Sierra 10.16.4
  • Node.js version (unless using Appium.app|exe): v8.6.0
  • Mobile platform/version under test: Nexus 5 X Api level 27 8.1 Oreo
  • Real device or emulator/simulator: Emulator
  • Appium CLI or Appium.app|exe: Appium CLI

Details

I see that in the Server there is a log entry: [debug] [UiAutomator2] [UIAutomator2] io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:INSTRUMENTATION_RESULT: shortMsg=Process crashed. This is returning a response in the Appium-Python-Client library (0.26):

{'status': 400, 'value': '{"value":{"message":"Could not proxy command to remote server. Original error: Error: read ECONNRESET","stacktrace":"ProxyRequestError: Could not proxy command to remote server. Original error: Error: read ECONNRESET\\n    at JWProxy.proxy$ (/usr/local/lib/node_modules/appium/node_modules/appium-base-driver/lib/jsonwp-proxy/proxy.js:152:13)\\n    at tryCatch (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40)\\n    at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:315:22)\\n    at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:100:21)\\n    at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)\\n    at <anonymous>"}}'}

Link to Appium logs

Full appium logs: https://gist.github.com/eduardoreynoso/22daff835172c52ccf5dd987f711465c

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:27 (1 by maintainers)

github_iconTop GitHub Comments

4reactions
auto-matorcommented, Jul 20, 2018

literally still occurs every 3 tests…

2reactions
mykola-mokhnachcommented, May 30, 2018
  • install appium
  • open /usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/lib or where the sources are located
  • change the necessary source file there
  • run gulp transplie in the same folder
  • restart appium server
Read more comments on GitHub >

github_iconTop Results From Across the Web

shortMsg=Process crashed. · Issue #15310 · appium ... - GitHub
The problem. INSTRUMENTATION_RESULT: shortMsg=Process crashed. Environment. Appium version (or git revision) that exhibits the issue: 1.20.2
Read more >
UIAutomator2 server 3.1.1 - Issues/Bugs - Appium Discuss
UIAutomator2 server 3.1.1 - INSTRUMENTATION_RESULT: shortMsg=Process crashed . The instrumentation process has been unexpectedly terminated.
Read more >
Instrumentation run failed due to 'Process crashed.'
I have a custom JUnitRunner and sometimes the test passes, on some occasions, it fails. Sometimes it crashes after test passes, sometimes all ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found