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

After bootstrapping cross-signing, you're prompted to verify yourself. #13203

Closed
ara4n opened this issue Apr 16, 2020 · 1 comment
Closed

After bootstrapping cross-signing, you're prompted to verify yourself. #13203

ara4n opened this issue Apr 16, 2020 · 1 comment

Comments

@ara4n
Copy link
Member

ara4n commented Apr 16, 2020

  • Log into riot 1.6 on a pre-cross-signing account
  • It prompts you to bootstrap via popup
  • After having bootstrapped, it tells you to 'verify your session' (sometimes this then disappears) - surely it should know to trust this session.
@ara4n ara4n added the T-Defect label Apr 16, 2020
@jryans jryans added S-Critical Prevents work, causes data loss and/or has no workaround cross-signing-sprint and removed S-Critical Prevents work, causes data loss and/or has no workaround labels Apr 16, 2020
@jryans
Copy link
Collaborator

jryans commented Apr 16, 2020

This sounds similar to #13181, but for the current device case. I assume the toast is waiting for remote echo of some data, so we'd need to resolve toasts locally / optimistically in some way to avoid this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants