Open ara4n opened 1 month ago
And even if the server had been upgraded, it would be rather nice to let the user export their keys or set up backup rather than nuking their history.
@Hywan It looks like the API was intentionally designed to not report an error? Should we be doing an extra check here before forcing the logout?
And even if the server had been upgraded
The banner shouldn't be shown if it hadn't been upgraded, we specifically check for native support before showing it. So the bug should be limited to the case where the well-known request fails but the /versions
request succeeds.
it would be rather nice to let the user export their keys or set up backup rather than nuking their history.
Unless the homeserver admin removed the proxy from the well-known at the point the user had bad connectivity, they will have already seen the banner that says if they don't do it now a force-logout will occur at some point:
Your server now supports a new, faster protocol. Log out and log back in to upgrade now. Doing this now will help you avoid a forced logout when the old protocol is removed later.
@pixlwave Can you open an issue on matrix-org/matrix-rust-sdk please, so that we can track this properly?
Steps to reproduce
Use EX on bad internet (on the tube)
See this:
Have no options other than hit 'logout'
Then discover that you don't know your recovery key, and get prompted to reset, and then freak out because you think you're going to lose your message history. (luckily in this instance there was another device logged in).
Outcome
What did you expect?
Never spontaneously log the user out (or force them to logout) due to bad internet connectivity.
Your phone model
No response
Operating system version
No response
Application version
1.8.4 (127)
Homeserver
matrix.org
Will you send logs?
Yes