Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Thanks for the bug report. If you can still reproduce this, can you attach a debugger and report what value for typeId you see in EncryptedSharedPreferences.getDecryptedObject?
ap...@google.com
The error reporting could be better. The next version will at least make it more clear what's going wrong.
jb...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit 168d2c90f6a88ff922d2ea72ac3a932c900e590b
Author: Daniel Angell <danielangell@google.com>
Date: Thu Oct 13 14:50:01 2022
Improve error reporting for getDecryptedObject()
Bug: 241699427
Test: Test suite passes. Difficult to add tests for specifically.
Change-Id: If6438b611a5a9ead4ae462cfa79f266ca65bc50d
M security/security-crypto/src/main/java/androidx/security/crypto/EncryptedSharedPreferences.java
https://android-review.googlesource.com/2254976
Branch: androidx-main
commit 168d2c90f6a88ff922d2ea72ac3a932c900e590b
Author: Daniel Angell <danielangell@google.com>
Date: Thu Oct 13 14:50:01 2022
Improve error reporting for getDecryptedObject()
Bug: 241699427
Test: Test suite passes. Difficult to add tests for specifically.
Change-Id: If6438b611a5a9ead4ae462cfa79f266ca65bc50d
M security/security-crypto/src/main/java/androidx/security/crypto/EncryptedSharedPreferences.java
Description
There are no use cases when we should allow a fragment's Lifecycle to be moved to
DESTROYEDother than when the fragment is actually destroyed.Therefore, you should not be able to
setMaxLifecycle()toDESTROYEDthrough aFragmentTransaction, initialize aFragmentScenariowithDESTROYED, or move aFragmentScenarioto theDESTROYEDstate usingmoveToState().Doing any of these things should throw an error.