ImmersiveModeConfirmation with Espresso 2.2.2

Question

Looks like some virtual devices on Google cloud test servers can't execute tests properly because of the Immersive mode confirmation popup (shown here: https://developer.android.com/training/system-ui/immersive.html) - is there a way to automatically close that popup with Espresso? Basically my code works in a local emulator, but not on Google cloud servers. This is what's failing:

View v = activity.getWindow().getDecorView();
v.setSystemUiVisibility(View.SYSTEM_UI_FLAG_LAYOUT_STABLE
    | View.SYSTEM_UI_FLAG_LAYOUT_HIDE_NAVIGATION
    | View.SYSTEM_UI_FLAG_HIDE_NAVIGATION
    | View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY);

score 1 · Answer 1 · answered May 08 '19 at 07:48

I have solved the problem using a similar version of @paul-t. Once the emulator has been started run the next command:

adb shell settings put secure immersive_mode_confirmations confirmed

After that you can execute your Espresso tests.

Inspiration: http://sviatoslavdev.blogspot.com/2018/02/adb-setings-secure.html

score 0 · Answer 2 · answered Jul 26 '17 at 19:20

0

You can run these ADB commands right after the emulator has started:

adb shell settings put secure immersive_mode_confirmations your.package.com
adb reboot (required)

immersive_mode_confirmations is a comma separated list of packages that no longer need confirmation for immersive mode

answered Jul 26 '17 at 19:20

Paul T

9
2

Unfortunately, that command didn't work :( This dialog is really annoying. – Benny Oct 24 '18 at 00:31
This may work if you have a rooted device I believe. – Benny Oct 24 '18 at 16:21
In the above example, replace "your.package.com" with "confirmed". Turns out Android doesn't want a list of packages. – J Smith Oct 14 '22 at 21:49

score 0 · Answer 3 · answered Oct 24 '18 at 16:26

I found a working solution. It's similar to Paul's answer but is by setting the permission programmatically before your tests run instead of using the ADB. There is a LinkedIn Open Source library that does everything for you, from getting WRITE_SECURE_SETTINGS permissions to changing the need for immersive confirmation dialog dynamically. After setting up the library, use the following line before your test starts:

TestButler.setImmersiveModeConfirmation(false);

For more details and setup instructions go here.

ImmersiveModeConfirmation with Espresso 2.2.2

3 Answers3