Google Fabric: UiAutomation not connected

AndroidCrashlyticsGoogle Fabric

Android Problem Overview


After deployment of an app to Google Play Beta I see next issue in Crashlytics (6 - 7 users are affected)

Fatal Exception: java.lang.IllegalStateException: UiAutomation not connected!
   at android.app.UiAutomation.throwIfNotConnectedLocked(UiAutomation.java:971)
   at android.app.UiAutomation.disconnect(UiAutomation.java:237)
   at android.app.Instrumentation.finish(Instrumentation.java:222)
   at android.support.test.runner.MonitoringInstrumentation.finish(MonitoringInstrumentation.java:351)
   at android.support.test.runner.AndroidJUnitRunner.finish(AndroidJUnitRunner.java:405)
   at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:394)
   at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1960)

It seems that it's google test devices. Any ideas about fix?

Android Solutions


Solution 1 - Android

It seems like nothing to worry about (don't rely on accepted answer and don't remove your tests) because crashes have been reported on creating pre-launch report for google play store where some UI automation tests were executed. If you track devices on which this error has occurred then you'll see that all paths lead to pre-launch report.

You can find out more about pre-launch report here

Solution 2 - Android

It seems that this crash is related to UI testing in your app. If you don't have any UI testing and there are only default settings which added automatically during creating the project, you should remove from your build.gradle the line testInstrumentationRunner in defaultConfig

  defaultConfig {
   ....
   testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
} 

and androidTestCompile, testCompile in dependencies

dependencies {
androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', 
{
    exclude group: 'com.android.support', module: 'support-annotations'
})
testCompile 'junit:junit:4.12'
...

Solution 3 - Android

One thing is sure: you have an issue on UI. In most cases this occurs when you show a progress dialog that keeps being displayed for too much time. In this case the Google crawler goes in timeout and raises an exception. My advice is: be sure to not block UI with infinite dialogs.

Solution 4 - Android

The funny thing is that I get this crash while my app is being tested by google before publishing. I really don't know what google team is doing.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionVitaliiView Question on Stackoverflow
Solution 1 - AndroidaresView Answer on Stackoverflow
Solution 2 - AndroidE IView Answer on Stackoverflow
Solution 3 - AndroidMariusz WiazowskiView Answer on Stackoverflow
Solution 4 - Androidصلي علي محمد Atef FaroukView Answer on Stackoverflow