Community-edition: Whatsapp Error (Needs Chrome 36+)

[mikeashelby]

I downloaded Rambox today, but the WhatsApp service isn't working. It Says:

WhatsApp works with Google Chrome 36+
To use WhatsApp, update Chrome or use Mozilla Firefox, Safari, Microsoft Edge or Opera.
UPDATE GOOGLE CHROME

Any ideas?

<!-- DON'T REMOVE THE FOLLOWING LINES -->
-
> Rambox 0.6.2
> Electron 2.0.8
> darwin x64 17.7.0

[welcome[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[valentine]

Adding on: it seems like there's some sort of feature detection because a simple User Agent change isn't working.

[mahovich]

+1

[stoque2]

I get the same issue. It worked once for me after launching it for the first time after upgrading from Ubuntu 16 to 18. It seems to have to do with an error in Whatsapp Web's browser detection.

[trinaldi]

Same with Arch Linux:

uname -a:
Linux 4.19.4-arch1-1-ARCH #1 SMP PREEMPT Fri Nov 23 09:06:58 UTC 2018 x86_64 GNU/Linux

About Rambox:

Version: 0.6.2
Platform: linux (x64)
Electron: 2.0.8
Chromium: 61.0.3163.100
Node: 8.9.3

Might as well reference #1979

[mikeashelby]

I noticed that the same is true on Franz, so I don't think it's a paid/free
thing - I would imagine it's happening on the paid version too. And also
could be an issue on WhatsApp's end with their browser detection rather
than rambox itself.

Still, somewhat frustrating to not be able to put all my messaging
platforms in one place!

That said, it's otherwise really awesome!

On Sun, 2 Dec 2018, 06:49 SBI-boy <[email protected] wrote:

It seems that nobody is answering here, it might be that the devs are only
focused in the paid version, it's a shame :/

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ramboxapp/community-edition/issues/1981#issuecomment-443485982,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKv7LIfyvxmjNnUEYaYASYkVp_ni8nVMks5u03f8gaJpZM4Y7ufr
.

[pbek]

for some reason I have the same problem on Windows, but not on Linux (KDE Neon and Manjaro) or macOS (High Sierra)

[stoque2]

What I've figured out so far is that going into developer tools (right click on Whatsapp tab) and selecting the memory tab, then deleting all site data resolves the issue but only until the next start of rambox.

[trinaldi]

@stoque2 That's a temporary solution as mentioned here (It's Franz repo, but the same error).

[pbek]

but not on Linux (KDE Neon and Manjaro) or macOS (High Sierra)

I take that back, after an app restart I have the same troubles...

[simonszu]

It seems that nobody is answering here, it might be that the devs are only focused in the paid version, it's a shame :/

Somewhere in here is a bug i have opened in 2017, with no reply so far except the autobot who tried to close it since there weren't any replies.

[trinaldi]

Franz seems to have fixed the issue.

[geek4teck]

Same issue on Windows 10 x64 & Ubuntu 16.04

Problem seems to be occuring 4 - 5 days back

[localhorst]

Same issue on Windows 10 x64
Problem seems to be occuring 4 - 5 days back

I am on a fresh install of Windows 10.
Same problem, it started yesterday (Dec 3, 2018)

Rambox Version: 0.6.2
Platform: win32 (x64)
Electron: 2.0.8
Chromium: 61.0.3163.100
Node: 8.9.3

Edit: I guess this will be hard to fix, because Whatsapp is eager to push their own Desktop app for Windows.

[localhorst]

So here is a workaround using a custom service:

Step 1
Create Custom service

Step 2
Name: Whatever
URL: https://web.whatsapp.com/
Logo: https://upload.wikimedia.org/wikipedia/commons/thumb/6/6b/WhatsApp.svg/64px-WhatsApp.svg.png

Step 3
Advanced - Custom Code:

function setUserAgent(window, userAgent) {
    // Works on Firefox, Chrome, Opera and IE9+
    if (navigator.__defineGetter__) {
        navigator.__defineGetter__('userAgent', function () {
            return userAgent;
        });
    } else if (Object.defineProperty) {
        Object.defineProperty(navigator, 'userAgent', {
            get: function () {
                return userAgent;
            }
        });
    }
    // Works on Safari
    if (window.navigator.userAgent !== userAgent) {
        var userAgentProp = {
            get: function () {
                return userAgent;
            }
        };
        try {
            Object.defineProperty(window.navigator, 'userAgent', userAgentProp);
        } catch (e) {
            window.navigator = Object.create(navigator, {
                userAgent: userAgentProp
            });
        }
    }
}

setUserAgent(window, "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36");

[mikeashelby]

Thanks for this! Brilliant!

On Tue, 4 Dec 2018 at 11:56, Mateng [e-mail] wrote:

So here is a workaround using a custom service:

Step 1
Create Custom service

Step 2
Name: Whatever
URL: https://web.whatsapp.com/
Logo:
https://upload.wikimedia.org/wikipedia/commons/thumb/6/6b/WhatsApp.svg/64px-WhatsApp.svg.png

Step 3
Advanced - Custom Code:

function setUserAgent(window, userAgent) {
// Works on Firefox, Chrome, Opera and IE9+
if (navigator.__defineGetter__) {
navigator.__defineGetter__('userAgent', function () {
return userAgent;
});
} else if (Object.defineProperty) {
Object.defineProperty(navigator, 'userAgent', {
get: function () {
return userAgent;
}
});
}
// Works on Safari
if (window.navigator.userAgent !== userAgent) {
var userAgentProp = {
get: function () {
return userAgent;
}
};
try {
Object.defineProperty(window.navigator, 'userAgent', userAgentProp);
} catch (e) {
window.navigator = Object.create(navigator, {
userAgent: userAgentProp
});
}
}
}

setUserAgent(window, "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36");

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ramboxapp/community-edition/issues/1981#issuecomment-444075137,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKv7LAiORfmWWuxdDCxlacCahEUuf48Jks5u1mMDgaJpZM4Y7ufr
.

[wgranicki]

@localhorst's workaround didn't work for me at first but after I've modified the last line, it works fine:
setUserAgent(window, "Chrome/70.0.3538.77");

Mind you, I have this exact version of Chrome installed.

EDIT: I take it back. After a while (and another restart of Rambox just to be sure), it doesn't work anymore :(

[rauldipeas]

WhatsApp back to work here, I don't used any fix.

[saenzramiro]

Overriding the User Agent seems like is not stable, because sometimes the warning comes again. We are currently investigating how to bypass this. Seems like WhatsApp want to prevent apps like us to use their service. 😭

@sudhagarc @andrewhassan Hey guys, any help with this, please? 🙏🏼

[mikeashelby]

Thanks Ramiro. I appreciate your time on the project!

On Tue, 4 Dec 2018 at 16:08, Ramiro Saenz [e-mail] wrote:

Reopened #1981
https://github.com/ramboxapp/community-edition/issues/1981.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ramboxapp/community-edition/issues/1981#event-2004732171,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKv7LD7tZ5aBPI7tsrBA2XUuYQs7cA7dks5u1p3qgaJpZM4Y7ufr
.

[Laski]

This is a duplicate of #1979

[saenzramiro]

@Laski Oh, but let's merge #1979 with this one.

[bjo81]

Strange, this issue appears on my desktop, but not on my laptop, both on Arch Linux with the same Rambox Version.

[simonszu]

@bjo81 same here. Both running latest Arch with a daily pacman syu.

[saenzramiro]

The pre-release v0.6.3 is available for those who want to test it.

[bjo81]

Same issue with 0.6.3.

[trinaldi]

@bjo81 I just upgrade my binaries (Arch Linux, as mentioned here]) and the issue is fixed.

Did you try cleaning up the storage, uninstalling the service (in this case WhatsApp) and installing again or even a full uninstall of the app?

[wgranicki]

Can confirm 0.6.3 works for me (Win 10).
The problem seemed to persist after an upgrade of Rambox, but after I'd reloaded the service, it worked.
Closing and reopening Rambox doesn't bring the problem back.

[bjo81]

@trinaldi Now it works, thanks.

[saenzramiro]

Yes guys, need a force-reload or removing WhatsApp and adding it again.

[roccomuso]

so what is the final fix?

[yafp]

so what is the final fix?

Removing and re-adding whatsapp helped for me (using 0.6.3)

[nasiralimx]

Well i have rambox on several machines but find this issue on Mac
what was useful on Mac was to delete the app preferences folder under
/Users/youruser/Library/Application\ Support/Rambox/
Probably will be needed to add the accounts all over again.
This was a quick fix im quite sure that will be other ones.
Hope it helps!

0,6,3

nasiralimx

[juliusHuelsmann]

I still have got the same issue on arch linux, fully updated with the Rambox 0.6.3 AppImage.

Edit: refreshing and / or rebooting helped :)

[driehle]

Updating to Rambox 0.6.3 and force-reloading solved the issue for me (Windows 10).

[lock[bot]]

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.