Fixed
Status Update
Comments
as...@google.com <as...@google.com>
ca...@google.com <ca...@google.com> #2
ViewModels need to be cleared on Fragments that are being really destroyed, where "really destroyed" means that they are being destroyed without their state being saved, indicating that there's no chance they are going to be restored at a later time.
Unfortunately, isStateSaved(), despite its name, does double duty as a check on whether it is safe to do Fragment Transactions and is always true after onStop(), meaning it can be true even if the state has really not been saved, oddly enough.
We'll just not use isStateSaved() here and rely on a separate indicator for the "really destroyed" case.
Unfortunately, isStateSaved(), despite its name, does double duty as a check on whether it is safe to do Fragment Transactions and is always true after onStop(), meaning it can be true even if the state has really not been saved, oddly enough.
We'll just not use isStateSaved() here and rely on a separate indicator for the "really destroyed" case.
it...@gmail.com <it...@gmail.com> #3
@ comment #2 Fixed in which version?
it...@gmail.com <it...@gmail.com> #5
We have to update compile SDK to 28 to adapt this fix?!
Description
androidx.core:core-splashscreen
1.0.0-beta01
Theme.SplashScreen
False
Pixel 4a (5G) (Android 11)
A small number of users are affected by this crash (report via
Crahlytics
) & it seems to be very device-specific (mentioned above).Stacktrace:
The
handleSeamlessEnd
extension method: