Hi @Nikita_Fedorishchev ,
Honestly, I was about to tell you that I didn’t really know what caused the issue and how I could reproduce, because these errors have been reported by users.
However, “by chance”, I encountered the same error on my computer, while developing.
My app ID is
Of course I went to have a look at the user in the database. I can’t see anything wrong with it. The user status is not Disabled.
So I immediately published the app in a folder, and created archives of that folder and of the UI builder container itself. Both archives can be found in the /render-error folder of my app.
To reproduce, I believe you would just need to launch the index.html with :
- the same Local Storage, which reads :
- the same session cookie, which is :
In fact, clearing the session cookie or restoring it didn’t do anything. However, clearing the Local Storage re-enabled the app, although in an unlogged state. And restoring the Local Storage reproduced the error. So my guess is that it’s coming from an issue in Local Storage.
Side note : it would be helpful that on this error screen, there could be perhaps a button which would reset the cookies and local storage. This way, users could at least resume using the app. Otherwise, on a mobile app, I find myself explaining to users that the workaround is to uninstall and reinstall the app. Not very user-friendly !
Side note 2 : is there a place where I can see the active user sessions ? I didn’t manage to find this, and it would help in understanding.