Skip to content

Keep what saved instance state is restored through - #875

Merged
JingMatrix merged 1 commit into
masterfrom
fix-enum-values-keep
Aug 5, 2026
Merged

Keep what saved instance state is restored through#875
JingMatrix merged 1 commit into
masterfrom
fix-enum-values-keep

Conversation

@JingMatrix

Copy link
Copy Markdown
Owner

Fixes #871, and #834 before it.

The manager crashes when its activity is restored after the host process has been reaped. Two keep rules are missing from manager/proguard-rules.pro, and the second one is only reachable once the first is in place.

Android resolves an enum's constants by reflective name lookup: Enum.valueOf asks the class for values(). Kotlin no longer calls that method itself — entries compiles to its own synthetic field — so the last call site is gone and R8 shrinks it away, from 105 of the 106 enums the released manager carries. An enum held in saved instance state goes into the Bundle as VAL_SERIALIZABLE, since Parcel has no enum case and java.lang.Enum is Serializable, and it can then no longer be read back. The navigation suite scaffold state is one such enum, and it sits above every screen.

CREATOR is found the same way, by a field lookup R8 cannot see, and it had been dropped from every Parcelable the manager does not already keep by name. A mutableStateOf that survives process death is a ParcelableSnapshotMutableState, so with the enums restored the same read fails with BadParcelableException instead.

Both stanzas are AGP's, from proguard-android-optimize.txt. That file stopped being passed to proguardFiles in #263. The manager it was dropped from copied the CREATOR rule back by hand and declared no enums at all, so neither rule was missed until #796.

Restoring the manager after its process had been reaped crashed, which is #871
-- and #834 before it, on Android 13. Two rules are missing, and the second one
only became visible once the first was in place.

R8 shrank values() out of 105 of the 106 enums in the released manager, because
nothing calls it any more: Kotlin compiles `entries` to a separate synthetic
field, so the generated method is left without a call site. Enum.valueOf looks
that method up by name, so an enum written into a Bundle -- Parcel has no enum
case and java.lang.Enum is Serializable, so it goes out as VAL_SERIALIZABLE --
cannot be read back. The navigation suite scaffold state is one such enum, and
it sits at the root of every screen.

CREATOR is found the same way, by a reflective field lookup R8 cannot see, and
it was gone from every Parcelable the manager did not already keep by name. A
`mutableStateOf` that survives process death is a ParcelableSnapshotMutableState,
so with the enums fixed the same restore threw BadParcelableException instead.

Both stanzas are AGP's, from proguard-android-optimize.txt. That file stopped
being passed to proguardFiles in #263, five years ago; the legacy manager had
copied CREATOR back by hand, the rewrite in #796 did not, and it declared no
enums at all, so neither rule was missed until the Compose manager needed them.

Verified on a Pixel 6 (Android 17) and a Galaxy A52s (Android 14): open the
manager, background it, kill the host process so the icicle comes back through
a Parcel, reopen. Before, that crashed every time; after, state restores across
repeated cycles, including the Logs tab and an open bottom sheet.
@JingMatrix
JingMatrix merged commit 481c139 into master Aug 5, 2026
1 check passed
suskie778 added a commit to suskie778/Vector that referenced this pull request Aug 5, 2026
Keep what saved instance state is restored through (JingMatrix#875)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Vector 2.2 (3080) Manager Crashes Randomly on Start

1 participant