Hello,
an error occures during logging in with the Tutanota-App. The message is “An error occured”.
With the browser it is very slow, but it works.
I have e OS 1.4 on an Samsung Galaxy Tab SM-T595.
I tried reinstallation several times but it is still the same. Does anybody has an idea?
Regards
if nothing helps, you could look at logcat what is happening while that error is thrown, it’s more verbose
Checking a tutanota forum can be helpful too, you cant be the only one running into this
Thanks. I just get a log from logcat: Many times it is said “Ein Netzwerkfehler ist aufgetreten.” (a network failure occured). Do you or anybody else has an idea about this?
Here is an excerpt of the logcat file:
10-20 13:19:41.368 3319 3896 V MainActivity: forwarding GET request to https://mail.tutanota.com/rest/sys/user/MR-dIRQ----2
10-20 13:19:41.492 3319 3896 V MainActivity: replacing OPTIONS response to https://mail.tutanota.com/rest/sys/groupinfo/MR-dIRS--J-2/MR-dIRw----2
10-20 13:19:41.496 3319 3319 E MainActivity: Error loading WebView -1 | Ein Netzwerkfehler ist aufgetreten. @ /rest/sys/groupinfo/MR-dIRS–J-2/MR-dIRw----2
10-20 13:19:41.498 3319 3896 V MainActivity: forwarding GET request to
the webview seems unable to handle the request, not sure if it hinges on the OPTIONS request.
As long as you can rule out any other network link error and other apps can do networking just fine, it’s the webview.
Maybe another /e/ 1.4 user with Tutanota can confirm the behaviour?
I still have the described problem. This is what the Tutanota app sends as a problem report:
Client: androidType: FREETutanota version: 3.104.5Timestamp (UTC): Fri, 02 Dec 2022 14:40:40 GMTUser agent:Mozilla/5.0 (Linux; Android 10; SAMSUNG SM-G960U Build/QQ3A.200805.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/100.0.4896.57 Mobile Safari/537.36java.security.KeyStoreExceptionError message: java.security.InvalidKeyException: Keystore operation failedStacktrace:java.security.KeyStoreException: java.security.InvalidKeyException: Keystore operation failedat de.tutao.tutanota.AndroidKeyStoreFacade.getCipherForEncryptionMode(AndroidKeyStoreFacade.kt:140)at de.tutao.tutanota.credentials.CredentialsEncryptionBeforeAPI30.encryptUsingKeychain(CredentialsEncryptionBeforeAPI30.kt:34)at de.tutao.tutanota.ipc.NativeCredentialsFacadeReceiveDispatcher.dispatch(NativeCredentialsFacadeReceiveDispatcher.kt:20)at de.tutao.tutanota.ipc.AndroidGlobalDispatcher.dispatch(AndroidGlobalDispatcher.kt:36)at de.tutao.tutanota.RemoteBridge.invokeMethod(RemoteBridge.kt:153)at de.tutao.tutanota.RemoteBridge.handleMessageFromWeb(RemoteBridge.kt:90)at de.tutao.tutanota.RemoteBridge$initMessageChannel$1$onMessage$1.invokeSuspend(RemoteBridge.kt:58)at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)Caused by: java.security.InvalidKeyException: Keystore operation failedat android.security.KeyStore.getInvalidKeyException(KeyStore.java:1373)at android.security.KeyStore.getInvalidKeyException(KeyStore.java:1413)at android.security.keystore.KeyStoreCryptoOperationUtils.getInvalidKeyExceptionForInit(KeyStoreCryptoOperationUtils.java:54)at android.security.keystore.KeyStoreCryptoOperationUtils.getExceptionForCipherInit(KeyStoreCryptoOperationUtils.java:89)at android.security.keystore.AndroidKeyStoreCipherSpiBase.ensureKeystoreOperationInitialized(AndroidKeyStoreCipherSpiBase.java:265)at android.security.keystore.AndroidKeyStoreCipherSpiBase.engineInit(AndroidKeyStoreCipherSpiBase.java:109)at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2984)at javax.crypto.Cipher.tryCombinations(Cipher.java:2877)at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2796)at javax.crypto.Cipher.chooseProvider(Cipher.java:773)at javax.crypto.Cipher.init(Cipher.java:1143)at javax.crypto.Cipher.init(Cipher.java:1084)at de.tutao.tutanota.AndroidKeyStoreFacade.getCipherForEncryptionMode(AndroidKeyStoreFacade.kt:135)… 12 moreCaused by: android.security.KeyStoreException: -62at android.security.KeyStore.getKeyStoreException(KeyStore.java:1303)… 24 more
Do you have any ideas what the problem is and how I can solve it?
android.security.KeyStoreException: -62
… what the errorcode 62? SO says https://stackoverflow.com/questions/58999536/android-security-keystoreexception-62 it’s a keymaster signal that somehow isn’t acted upon.
Upgrades an old key. Keys can become “old” in two ways: Keymaster can be upgraded to a new version, or the system can be updated to invalidate the OS version and/or patch level. In either case, attempts to use an old key will result in keymaster returning KM_ERROR_KEY_REQUIRES_UPGRADE. This method should then be called to upgrade the key.
I don’t know what it doesn’t like. You could reinstall tutanota and wipe it’s app cache etc. Could be related to device state? keymaster holds keys in the TEE (trusted exec environment) zone of the device
Would be nice to have confirmation by at least 1 other tutanota user that things are supposed to work 