-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Prevent the user from creating multiple devices whereas a session is available #11643
Closed
Labels
Comments
Great idea! Few questions:
|
If the app detects that the user is already logged in, it should be able to redirect to the main screen with no interaction, and allow the user to just start using Riot. |
We're tracking this in #12476 |
This comment has been minimized.
This comment has been minimized.
t3chguy
added a commit
to matrix-org/matrix-react-sdk
that referenced
this issue
Jun 2, 2020
due to fragmentAfterLogin going back to `#/login` and element-hq/element-web#11643 Signed-off-by: Michael Telatynski <[email protected]>
t3chguy
added a commit
that referenced
this issue
Jun 2, 2020
due to fragmentAfterLogin going back to `#/login` and #11643 Signed-off-by: Michael Telatynski <[email protected]>
This was referenced Jun 2, 2020
t3chguy
added a commit
to matrix-org/matrix-react-sdk
that referenced
this issue
Jun 3, 2020
due to fragmentAfterLogin going back to `#/login` and element-hq/element-web#11643 Signed-off-by: Michael Telatynski <[email protected]>
t3chguy
added a commit
that referenced
this issue
Jun 3, 2020
due to fragmentAfterLogin going back to `#/login` and #11643 Signed-off-by: Michael Telatynski <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some Riot-web users add to their Favourites or Bookmarks the welcome or the login url screen.
When these users want to go back to Riot, they land on the login screen and fill their credentials. This creates a new device in their account (most of them are not aware of that). They don't understand why the app fails to decrypt the room history in the encrypted rooms.
Would it be possible to check the local storage when the login screen is loaded by the browser in order to prevent them from logging in again?
The text was updated successfully, but these errors were encountered: