-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
Android: Encryption support silently breaks #129
Labels
stale
The item is going to be closed soon because of inactivity
Comments
Closed
Closed
This issue is stale because it has been open for 120 days with no activity. |
github-actions
bot
added
the
stale
The item is going to be closed soon because of inactivity
label
Mar 6, 2024
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Essential encryption featues seem to be unavailable on my Android device, it looks like FluffyChat enters a failure mode. After login, I am not asked to verify the device, and in the Settings -> Security page, the menu items for my public key and key backup are simply missing, I only see the points “Ignored users”, “Change password” and “Password recovery”. On the in-browser version of FluffyChat on my desktop everything works as expected though. With FluffyChat Android I can't read any of the encrypted chats and FluffyChat sends unencrypted messages even into encrypted chat rooms.
Furthermore, I cannot verify the FluffyChat Android session from Element. Element desktop doesn't list the session in the verification panel, although I can see it in the session management setttings. Element Android lists the session, but says “No cryptographic information available” for my FluffyChat Android session, so I can't start the verification there either.
Sadly,
logcat
doesn't seem to provide any useful information:To Reproduce
Additional information:
The text was updated successfully, but these errors were encountered: