You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A short session is limited by time, and something produces a weird reaction that causes the application to ask for an account password after clicking the submit button in the short session. This produces a suspended status because the user doesn't have enough time to enter the password. So far, we have a list of facts that are somehow related to this problem:
The user interface is not in English (I'm not sure if this is because of automatic translation or language properties in the application settings).
If the auto-translate function is switched on, when you uploading your flips to the blockchain, they would be uploaded with a connection to another pair of keywords not the same pair that have been loaded in the editor.
If you switch on the auto-translate function and click on the button to mark a specific flip as the best one, the application asks you for your account password again.
There is a big chance that this strange behavior is somehow related to the auto-translate function.
Maybe it is just a coincidence, but in most cases that produce a password prompt after clicking the submit button in the short session, there are 1-2 flips that have not been loaded at the end of the list.
Because time in the short session is critical, would it be possible for that part of the ceremony to keep the app authorized even if the page is reloaded or the connection is broken? I think that would be an acceptable solution. For now, in most cases, the user's account becomes suspended.
The text was updated successfully, but these errors were encountered:
A short session is limited by time, and something produces a weird reaction that causes the application to ask for an account password after clicking the submit button in the short session. This produces a suspended status because the user doesn't have enough time to enter the password. So far, we have a list of facts that are somehow related to this problem:
Because time in the short session is critical, would it be possible for that part of the ceremony to keep the app authorized even if the page is reloaded or the connection is broken? I think that would be an acceptable solution. For now, in most cases, the user's account becomes suspended.
The text was updated successfully, but these errors were encountered: