Wrong screen is resumed when popping screens sequentially [177590791]

Fixed

Bug

Status Update

No update yet.

Description

mi...@gmail.com

created issue #1

Jan 15, 2021 03:42AM

Library version used: 1.0.0-beta.1
Devices/Android versions reproduced on: Pixel 5/Android 11, DHU
Android Auto version reproduced on: 5.8.604354-release

Situation

Sample project to trigger the issue: https://github.com/themics/android-auto-screen-stack-bug

Let's say we have a screen stack of [A, B, C]. A is the root, and C is the top.

B is pushed by A for some result via screenManager.pushForResult(). So is C by B.

When C set the result and finish() itself, B also set that result and finish() itself to relay the result to A.

Now we have [A] and A is resumed properly. C and B is destroyed as well.

Problem

B's lifecycle is resumed again.

Log

(open an app)
12:35:00.566 I/AScreen: state: ON_CREATE
12:35:00.577 I/AScreen: state: ON_START
12:35:00.579 I/AScreen: state: ON_RESUME

(push B)
12:35:02.325 I/BScreen: state: ON_CREATE
12:35:02.326 I/BScreen: state: ON_START
12:35:02.326 I/AScreen: state: ON_PAUSE
12:35:02.327 I/AScreen: state: ON_STOP
12:35:02.327 I/BScreen: state: ON_RESUME

(push C)
12:35:03.521 I/CScreen: state: ON_CREATE
12:35:03.522 I/CScreen: state: ON_START
12:35:03.522 I/BScreen: state: ON_PAUSE
12:35:03.522 I/BScreen: state: ON_STOP
12:35:03.522 I/CScreen: state: ON_RESUME

(pop C & B)
12:35:04.441 I/BScreen: state: ON_START
12:35:04.442 I/CScreen: state: ON_PAUSE
12:35:04.442 I/CScreen: state: ON_STOP
12:35:04.442 I/AScreen: state: ON_START
12:35:04.442 I/BScreen: state: ON_STOP
12:35:04.443 I/BScreen: state: ON_DESTROY
12:35:04.443 I/AScreen: state: ON_RESUME
12:35:04.444 I/CScreen: state: ON_DESTROY
12:35:04.444 I/BScreen: state: ON_CREATE   <- problem
12:35:04.444 I/BScreen: state: ON_START    <- problem
12:35:04.444 I/BScreen: state: ON_RESUME   <- problem

Comments

jo...@google.com <jo...@google.com> #2Jan 20, 2021 07:29PM

Assigned to li...@google.com.

I have updated AS to version 4.1.3 and the android emulator to version 30.5.3.0. Now I can't use the emulator anymore. I have Mojave OS installed and I confirm the same message described in previous post. The file does not exist in the file system.

li...@google.com <li...@google.com> #3Jan 25, 2021 10:20PM

As a workaround, I was able to successfully downgrade android emulator to 28.

See: https://stackoverflow.com/questions/49120854/how-to-downgrade-android-emulator

I downloaded 28.0.25.0 (build_id 5395263) from here:

https://dl.google.com/android/repository/emulator-darwin-5395263.zip

I deleted everything EXCEPT package.xml from

$HOME/Library/Android/sdk/emulator/

and replaced them with the contents of the extracted zip file.

Finally, make sure your AVD system image is NOT running api 30.

sdkmanager "system-images;android-27;google_apis_playstore;x86"

System images higher than api 29 are using a kernel format that the older emulator cannot understand.

Here's a workaround script you can try:

cd ~
mkdir emulator_downgrade
cd emulator_downgrade
wget https://dl.google.com/android/repository/emulator-darwin-5395263.zip
unzip emulator-darwin-5395263.zip
mv ~/Library/Android/sdk/emulator ~/Library/Android/sdk/previous-emulator
mv emulator ~/Library/Android/sdk/emulator
cp ~/Library/Android/sdk/previous-emulator/package.xml 
~/Library/Android/sdk/emulator/package.xml
cd ~
~/Library/Android/sdk/emulator/emulator -version
~/Library/Android/sdk/emulator/emulator -list-avds

jo...@google.com <jo...@google.com> #4Feb 2, 2021 05:27PM

Thank you for the downgrade explanation. If you want to use a more recent emulator 30.1.5 the build number is 6855416. I believe you can use this build with API 30 images without issues.

sh...@google.com <sh...@google.com> Feb 11, 2021 05:31PM

Marked as fixed.

ag...@gmail.com <ag...@gmail.com> #5Mar 4, 2021 06:17PM

I am facing the same issue. Can't run emulator after upgrading to version 30.5.3. My macOS is Mojave 10.14.6.