-
Notifications
You must be signed in to change notification settings - Fork 734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backing up keys makes Element crash #2262
Comments
Deleting key backup from Element-Desktop stopped the crash, so I was able to send a rageshake this way. Let me know if there's anything else I can do to help figure this out. |
I'm having the same error with galaxy s9+ |
I am having the exactly same issue
Device
App version
|
Somehow the val sessionBackupData = mapOf(
"algorithm" to sessionData?.algorithm,
"sender_key" to sessionData?.senderKey,
"sender_claimed_keys" to sessionData?.senderClaimedKeys,
"forwarding_curve25519_key_chain" to (sessionData?.forwardingCurve25519KeyChain
?: ArrayList<Any>()),
"session_key" to sessionData?.sessionKey) The removal of the null-safety "!!" makes the app not crash anymore, but it is obviously no solution for the problem that this was |
The pull request says that it fixes the crash but not the root cause. What is the root cause and is this something we can get rid of ourselves? |
Describe the bug
If I restore my backup (doesn't matter if via QR code or recovery key) the app just keeps crashing all the time. After starting it up again it crashes to fast to send a rageshake, but logcat gives me the following:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No crash
Smartphone (please complete the following information):
Additional context
It might also have something to do with element-hq/element-web#15388
The text was updated successfully, but these errors were encountered: