Community-edition: Rambox does not start after upgrade to 0.5.1 (endless loading animation)

Created on 26 Jan 2017  路  11Comments  路  Source: ramboxapp/community-edition

After upgrading from Rambox 0.4.5 to 0.5.1 rambox does still start but it is stuck at the loading animation. There is an error in the dev console (See screenshot)

The (now broken) profile had been configured with several services (Whatsapp, Slack, Skype) and was synchronized with a Rambox account.

This might have something to do with connectivity to the Rambox Account/Syncing service. After deleting the profile in ~/.config/Rambox rambox loaded fine but clicking on "Login" resulted in a endless loading of the Rambox Account modal.
Next start it did load - so not sure if this is connected to the described issue after upgrading.

I kept a copy of the working profile before the upgrade and the broken profile after the upgrade to be able to reproduce the issue.

Thanks for continuing development/fixing the annoying certificate bug :)

ENVIRONMENT

Rambox: v0.5.1
OS: Arch Linux
Arch: x64

image

Most helpful comment

Done :)

All 11 comments

After upgrading from Rambox 0.4.5 to 0.5.2 - i have this issue

OS: MacOS 10.11

I have made fix to application and repacked app.asar.
You have to put it into rambox install directory, in my case it is:
c:\Users\\AppData\Local\Rambox\app-0.5.2\resources\app.asar
I don't know where rambox install on other OSes.

@bjab could you make a pull request for the fix so it can go into the code proper? :)

Done :)

in macOS /Applications/Rambox.app/Contents/Resources

But connect to Auth0 not working?
I see only
"Please wait until we get your configuration."

My solution is only for incompatibility of profile data between versions in localStorage.
I think, that problem of translating old user profile to new between Auth0 and local Rambox must be resolved by developers.

same error here - also with macOS 10.12.2
thx to @bjab for this solution - it helped me to start the app :)

Please update to latest version 0.5.3.

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.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

andrii-riabchun picture andrii-riabchun  路  3Comments

Tseberechts picture Tseberechts  路  4Comments

juanmlambre picture juanmlambre  路  3Comments

mforcer picture mforcer  路  3Comments

saalkom picture saalkom  路  3Comments