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