17dc2949-2a31-4b96-b6cd-bd1651ab510a javax.crypto.IllegalBlockSizeException
Categories
(Firefox for Android :: Accounts and Sync, defect)
Tracking
()
People
(Reporter: Webworkr, Unassigned)
References
()
Details
(Keywords: crash)
User Agent: Mozilla/5.0 (Android 14; Mobile; rv:131.0) Gecko/131.0 Firefox/131.0
Steps to reproduce:
Crash while using private mode
Actual results:
17dc2949-2a31-4b96-b6cd-bd1651ab510a
javax.crypto.IllegalBlockSizeException
javax.crypto.IllegalBlockSizeException
at android.security.keystore2.AndroidKeyStoreCipherSpiBase.engineDoFinal(AndroidKeyStoreCipherSpiBase.java:634)
at javax.crypto.Cipher.doFinal(Cipher.java:2056)
at mozilla.components.lib.dataprotect.SecurePreferencesImpl23.putString(SecureAbove22Preferences.kt:86)
at mozilla.components.lib.dataprotect.SecureAbove22Preferences.putString(SecureAbove22Preferences.kt:8)
at mozilla.components.service.fxa.SecureAbove22AccountStorage.write(AccountStorage.kt:10)
at mozilla.components.service.fxa.StorageWrapper$PersistenceCallback.persist(AccountStorage.kt:44)
at mozilla.components.service.fxa.FirefoxAccount$WrappingPersistenceCallback.persist(FirefoxAccount.kt:38)
at mozilla.appservices.fxaclient.FxaClient.tryPersistState(FxaClient.kt:9)
at mozilla.appservices.fxaclient.FxaClient.access$tryPersistState(FxaClient.kt:1)
at mozilla.appservices.fxaclient.FxaClient$getAccessToken$1.invoke(FxaClient.kt:3)
at mozilla.appservices.fxaclient.FxaClient$getAccessToken$1.invoke(FxaClient.kt:1)
at mozilla.appservices.fxaclient.FxaClient.withMetrics(FxaClient.kt:16)
at mozilla.appservices.fxaclient.FxaClient.getAccessToken(FxaClient.kt:12)
at mozilla.appservices.fxaclient.FxaClient.getAccessToken$default(FxaClient.kt:6)
at mozilla.components.service.fxa.FirefoxAccount$getAccessToken$2$2.invokeSuspend(FirefoxAccount.kt:14)
at mozilla.components.service.fxa.FirefoxAccount$getAccessToken$2$2.invoke(FirefoxAccount.kt:11)
at mozilla.components.service.fxa.UtilsKt.handleFxaExceptions(Utils.kt:6)
at mozilla.components.service.fxa.UtilsKt.handleFxaExceptions(Utils.kt:23)
at mozilla.components.service.fxa.FirefoxAccount$getAccessToken$2.invokeSuspend(FirefoxAccount.kt:43)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:111)
at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:4)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:3)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:98)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@3b6621c, Dispatchers.Main]
Caused by: android.security.KeyStoreException: Invalid operation handle (internal Keystore code: -28 message: system/security/keystore2/src/operation.rs:836: KeystoreOperation::update
Caused by:
0: In update
1: system/security/keystore2/src/operation.rs:325: Call on finalized operation with outcome: Pruned.
2: Error::Km(r#INVALID_OPERATION_HANDLE)) (public error code: 15 internal Keystore code: -28)
at android.security.KeyStore2.getKeyStoreException(KeyStore2.java:435)
at android.security.KeyStoreOperation.handleExceptions(KeyStoreOperation.java:78)
at android.security.KeyStoreOperation.update(KeyStoreOperation.java:115)
at android.security.keystore2.KeyStoreCryptoOperationChunkedStreamer$MainDataStream.update(KeyStoreCryptoOperationChunkedStreamer.java:222)
at android.security.keystore2.KeyStoreCryptoOperationChunkedStreamer.update(KeyStoreCryptoOperationChunkedStreamer.java:156)
at android.security.keystore2.KeyStoreCryptoOperationChunkedStreamer.doFinal(KeyStoreCryptoOperationChunkedStreamer.java:179)
at android.security.keystore2.AndroidKeyStoreCipherSpiBase.engineDoFinal(AndroidKeyStoreCipherSpiBase.java:624)
... 23 more
Expected results:
No crash
| Reporter | ||
Comment 1•1 year ago
|
||
"Settings" menu > "About Firefox Nightly" > "Crashes":
There are no existing crash reports linked so far.
Comment 2•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::Accounts and Sync' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 3•1 year ago
|
||
Thanks for the report!
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Updated•1 year ago
|
Description
•