Skip to content
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

"Enter recovery key" on fresh install verified session #3469

Closed
ccrvlh opened this issue Nov 1, 2024 · 2 comments
Closed

"Enter recovery key" on fresh install verified session #3469

ccrvlh opened this issue Nov 1, 2024 · 2 comments
Labels

Comments

@ccrvlh
Copy link

ccrvlh commented Nov 1, 2024

Steps to reproduce

Download Element X iOS
Login with user/password
Verify session from another device
See the list of chats, with a banner: "Enter your recovery key" (I don't have one), although I do have 3 logged devices.
All chats don't have history, even the rooms that are marked with "Members since they were invited" Read History permission.

Outcome

What did you expect?

Access chat history.
No warning message.

What happened instead?

Can't read history, chat backup out of sync

Your phone model

iPhone 13

Operating system version

iOS 17.6.1

Application version

1.9.3 (134)

Homeserver

matrix.org

Will you send logs?

Yes

@ccrvlh ccrvlh added the T-Defect label Nov 1, 2024
@ccrvlh
Copy link
Author

ccrvlh commented Nov 1, 2024

Was able to get it working by reseting the backup and generating a new key.
Forgive my ignorance on the matter - but why would that be necessary even after verification using another device? If the I was able to verify my session through another device, I do have access to that device, so I can go through the process to reset the backup / generate new keys.

@pixlwave
Copy link
Member

pixlwave commented Nov 1, 2024

Looks like you've fixed this so I'm going to close the issue. The banner was shown because even after verifying with another device, your key storage/backup wasn't able to fully sync. We've tidied up the banner for the next release to help communicate this out-of-sync state:

#3468

@pixlwave pixlwave closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants