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

WhatsApp not loading #1985

zu opened this Issue Dec 3, 2018 · 7 comments


None yet
8 participants

zu commented Dec 3, 2018

<!-- Please describe here your issue and steps to reproduce it. -->

Suddenly the WhatsApp window just states that it needs Chrome 36+ and prompts me to update Google Chrome.
I'm actually on version 70.

> Rambox 0.6.2
> Electron 2.0.8
> darwin x64 18.2.0

@zu zu changed the title from WhatsApp not to WhatsApp not loading Dec 3, 2018


This comment has been minimized.

wstrik commented Dec 3, 2018

Issue disappeared, probably an issue at web Whatsapp.


This comment has been minimized.

hOlYxY commented Dec 3, 2018

Just open your Chrome Browser and open Whatsapp Web in a new tab. Login and then switch back to Rambox, it should work after you reloaded the Whatsapp application in Rambox.


This comment has been minimized.

mheindl commented Dec 3, 2018

thx @hOlYxY , worked for me as well. Just a app restart was needed ;-)


This comment has been minimized.

GeeBee93 commented Dec 3, 2018

Is there somehow a possibility to change the user agent? I just found an older PR which has never been merged to change the user agent for all services. I was not able to find a way to change the user agent through injected JS code either.

This could maybe fix this bug (?)


This comment has been minimized.

arnaudlorioz commented Dec 3, 2018

just tried to open whatsapp web, then switch back to rambox and reload whatsapp....without success


This comment has been minimized.

Muenze commented Dec 3, 2018

I also tried it, go to with my chrome, log in there, restart Rambox ... again => update chrome


This comment has been minimized.


saenzramiro commented Dec 4, 2018

Merged with #1981.

saenzramiro added a commit that referenced this issue Dec 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment