I am also experiencing this bug. I also made a test application that experiences the same indefinite hanging on Android 11: https://github.com/prfarlow1/UiTestApplication

Same issue is occurring when compiling and targeting SDK 30 and running against an emulator with 30.

2020-09-21 14:26:44.942 31419-31419/com.scompany.consumer E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.scompany.consumer, PID: 31419
java.lang.RuntimeException: Exception thrown in onCreate() of ComponentInfo
java.lang.RuntimeException: Cannot connect to androidx.test.orchestrator.OrchestratorService
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6709)
at android.app.ActivityThread.access$1300(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7656)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
Caused by: java.lang.RuntimeException: Cannot connect to androidx.test.orchestrator.OrchestratorService

• no issue when compiling and targeting 30 and running on an emulator with 29.
• no issue when compiling and targeting 29 and running on an emulator with 30.

Can we get an update from the Android test team when this will be addressed? This is a really bad bug. We rely on the orchestrator for our tests to pass and right now we just can't run our tests on Android 11 test devices.

Same here. Everything was working fine with emulator api 29 and Orchestrator until we migrated to api 30.

Hey all, sorry for delayed response. We are looking into this, but the fix is proving more difficult to get released than anticipated. We hope to have something out soon to address this.

Same here. Switched to Android 10 and it's working fine for me.

Please give 1.3.1-alpha01 a try. This should hopefully be fixed.
See https://github.com/android/android-test/releases/tag/androidx-test-1.3.1-alpha01

Can't confirm it works :/ It doesn't hang indeed, but still fails with a message:

Task :app:connectedDebugAndroidTest
Starting 0 tests on test(AVD) - 11
Tests on test(AVD) - 11 failed: Instrumentation run failed due to 'Process crashed.'

com.android.build.gradle.internal.testing.ConnectedDevice > No tests found.[test(AVD) - 11] FAILED
No tests found. This usually means that your test classes are not in the form that your test runner expects (e.g. don't inherit from TestCase or lack @test annotations).

Failed run:
https://github.com/mateuszkwiecinski/orchestrator_doesnt_work/pull/3/checks?check_run_id=1274143298

It works on devices with api <30

I also could not get my tests to work with the new 1.3.1-alpha01

It looks like there is an incompatibility with the testInstrumentationRunnerArguments clearPackageData: 'true' setting. I was able to get @mateuszkwiecinski sample working by commenting out that line.

A workaround for the clearPackageData issue is to declare a

application android:forceQueryable="true"

in the androidTest manifest

A workaround for the clearPackageData issue is to declare a

application android:forceQueryable="true"

in the androidTest manifest

What does android:forceQueryable="true" actually do? I can't find any documentation for it

Check out the docs on the new package visibility restrictions on API 30 here
https://developer.android.com/training/basics/intents/package-visibility

IIUC using forceQueryable basically lets other apps (like the orchestrator app) communicate with the test package.

Please give 1.3.1-alpha02 a try

Thank you @brettchabot 👍
I can confirm it works in my sample project 🚀

whew thanks for confirming @mateuszkwiecinski

android:forceQueryable isn't recognized by AAPT2 4.1.0 and fails the build:

Execution failed for task ':Mobile-Android:processDevDebugAndroidTestResources'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > Android resource linking failed
     /home/tad/simple/mobile/Mobile-Android/Mobile-Android/build/intermediates/packaged_manifests/devDebugAndroidTest/AndroidManifest.xml:22: AAPT: error: attribute android:forceQueryable not found.
         

@tadfisher can you be more specific about your project setup? I don't know where a 'AAPT2 4.1.0' comes from.

The aapt2 version in build tools 30.0.2 appears to be
~/Android/Sdk/build-tools/30.0.2$ ./aapt2 version
Android Asset Packaging Tool (aapt) 2.19-6739378

@brettchabot My bad, this is on a nonstandard setup using aapt2 from maven.google.com. With the aapt2 packaged with build-tools 30.0.2, this works.

@tadfisher cool thanks for confirming.

@brettchabot Just in case if that's related: I faced another issue with 1.3.1-alpha02 - our tests don't fail anymore. Apparently new alpha version changes when org.junit.runner.notification.RunListener callbacks are called, which breaks LeakCanary, which throws an exception and for an unknown reason makes the test to pass.
I reported an issue there (square/leakcanary#1986) but as well that might be an unexpected behavior change in the android-test library