<!-- Please describe here your issue and steps to reproduce it. -->
1) Go to Rambox setup
2) Click on Backup preferences
3) Get a popup saving..
It't get stuck there forever. I need to reload Rambox to be able to continue working. (attaching the screen shot)

<!-- DON'T REMOVE THE FOLLOWING LINES -->
-
> Rambox 0.5.17
> Electron 1.8.4
> linux x64 3.10.0-862.11.6.el7.x86_64
Same here, also when you need to restore a backup from another Rambox instance authentication fails
I am having the same issue with latest version installed. Backup is stuck on the "Saving backup..." overlay.
Also note that the Delete also will get stuck on "Please wait until we clear all." when an item is disabled (unchecked).
same here. would be important a day.
Mehh.. i came back to Franz.
Rambox Devs are only dedicating their time to payment version
Same, even on the updated 0.6.1, Windows 10.
Version: 0.6.1
Platform: win32 (x64)
Electron: 2.0.8
Chromium: 61.0.3163.100
Node: 8.9.3
_Edit:_ Mentioned below about losing logins. This didn't happen for me after hitting Reload once it was stuck, though it did happen when updating to 0.6.1.
Same bug for me.. It's quite anoying .. And after it gets stuck I lose all my login :(
EDIT : I am using Macbook pro 2018
same here, just created another issue for it, will close newly created issue, ubuntu 16.04.5 kernel 4.15
Same, even on the updated 0.6.1, Windows 10.
Version: 0.6.1 Platform: win32 (x64) Electron: 2.0.8 Chromium: 61.0.3163.100 Node: 8.9.3_Edit:_ Mentioned below about losing logins. This didn't happen for me after hitting Reload once it was stuck, though it did happen when updating to 0.6.1.
Same happening here :~
Same issue on Windows 10 and Debian - testing 4.18.0-1-amd64.
Version: 0.6.1
Platform: linux (x64)
Electron: 2.0.8
Chromium: 61.0.3163.100
Node: 8.9.3
Still happening as others stated, after upgrading.. .and interestingly I found another issue..

Same problem on 5.x versions and 0.6.0, 0.6.1 too - infinite loop of progress bar in saving backup window. Reproduced with new empty profile too.
I can confirm the issue is still happening after upgrading to 0.6.1
OK, opening up Dev Tools, looks like the Auth0 stuff is wrong. I see two failing requests:
PATCH https://rambox.auth0.com/api/v2/users/undefined 401 ()
{
"statusCode": 401,
"error": "Unauthorized",
"message": "Expired token received for JSON Web Token validation",
"attributes": { "error": "Expired token received for JSON Web Token validation" }
}
app.js:1 POST https://rambox.auth0.com/delegation 401 ()
{
"error": "invalid_client",
"error_description": "OIDC conformant clients cannot use /delegation",
"statusCode": 401
}
Guessing the Auth0 stuff needs updating (and the UI to handle this blowing up gracefully instead of just stalling forever). I'd take a look, but I've had issues running Rambox from source locally.
On my side with the dev tools open the problem seems to be a failed call to : https://rambox.auth0.com/api/v2/users/google-oauth
I tried to setup the env locally to be able to try and debug this issue since this and https://github.com/ramboxapp/community-edition/issues/1888 is stopping me from being able to setup and use rambox completly now. It will take me a little while since I have to figure out how the auth0 app is setup to be able to use my auth0 account instead. If there is documentation on that part anywhere I would appreciate the link and will try to fix.
This is regarding Auth0 changes and deprecations. We will fix this in the next version coming soon.
v0.6.1 still have the issue + I don't want to update before backing up...
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
OK, opening up Dev Tools, looks like the Auth0 stuff is wrong. I see two failing requests:
PATCH https://rambox.auth0.com/api/v2/users/undefined 401 ()app.js:1 POST https://rambox.auth0.com/delegation 401 ()Guessing the Auth0 stuff needs updating (and the UI to handle this blowing up gracefully instead of just stalling forever). I'd take a look, but I've had issues running Rambox from source locally.