Isaac A. Murchie

What do you get if you run ``` C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s BUC4C16C16005142 shell dumpsys package io.appium.uiautomator2.server.test ```

This should no longer happen, with [this change](https://github.com/appium/appium-uiautomator2-driver/pull/262). Please try with the latest beta (`npm uninstall -g appium && npm install -g appium@beta`).

Sorry for the lateness of this. This repo is not checked for issues. But I cannot get this to reproduce. Do you happen to have Appium server logs for this?...

Can you please post the full Appium server logs, as a link to a [gist](https://gist.github.com)? There is nothing that can be done with the information given at present.

@zengxiaoshi Please, if you have a working solution that implements this idea, please submit a PR. We would be happy to get this functionality in Appium and you seem the...

@zengxiaoshi That would be a breaking change that would not be easily accommodated. It is possible that the reverse could be done (i.e., try by desc, then by text).

I apologize if this is off-base, but I have an error that presents as the same error. Environment: * Node: v8.14.0 * Npm: 6.4.1 * mocha-parallel-tests: 2.0.6-alpha.3 * mocha: 5.2.0...

We just have a [little gulp task to fix the issue](https://github.com/appium/appium-gulp-plugins/blob/master/lib/tasks/ci.js#L40-L56) in our build pipeline. Not the greatest solution, but until something is addressed here, one that works.

Moving to the Java client, which may have more help.

What are the details of the Appium service running? Appium version? Logs? It _really_ helps with diagnosing.