Arch Linux User Repository

Warning to all existing users: Nativefier is now unmaintained (https://github.com/nativefier/nativefier/issues/1577)

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.whatsapp-nativefier/releases/

Hey guys,

I created the original fix.

And now I share another way to use whatsapp web on nativefier. No code injection required.

Pressing ctrl+shift+i (on Linux) and the Devtools window will open. Then click on Application -> Service Workers And check the option Bypass for network.

Now press ctrl+r to reload. And ctrl+shift+i to close the Devtools.

Whenever you open your whatsapp the problem will occur, but since the Bypass for network option has already been enabled, you only need to press ctrl+shift+i (open devtools), ctrl+r (reload), ctrl+shift+i (close devtools)

@frealgagu, thanks for your work. This package was in my list as one of required apps to be installed after install Arch. I saw your last update ( document.querySelector("a[href='https://support.google.com/chrome/answer/95414']") ), NICE/GREAT/GOOD!

Another way to do the same in 2 lines: document.querySelector("a[href='https://support.google.com/chrome/answer/95414']") && navigator.serviceWorker.getRegistration().then(r => r.unregister() && document.location.reload());

If you remove the --browserwindow-options '{ "webPreferences": { "spellcheck": true } }' it works perfectly

Edit: After the latest update this method does not work anymore, the only way i managed to get it working was through the devtools method

On startup, whatsapp-nativefier now complains about "Old build detected. This app was built a long time ago."

EDIT: Made a PR to resolve that.

Any way to keep the same window size? at each start it resets

An easy workaround for the "What's App works with Google Chrome 60+" issue is to open Devtools panel (ctrl+shift+i) then follow these steps:

• click on Application -> Service Workers and check the option Bypass for network ( this step was described by @saulcastelo )

• then navigate to More tools > Network conditions and at User Agent uncheck "Select automatically" and choose another user agent from the list. (I am currently getting good results with the "Firefox -- Windows" option, but this might change at some point).

Now Ctrl+R and closing the developers tools (Ctrl+Shift+i).

Ctrl+shift+i then Ctrl+r is still required occasionally when all that is shown is a blank screen.

I am getting the following error as well:

"What's App works with Google Chrome 60+"

Workaround is to use the web client on any browser.

@nursoda nativefier uses electron as browser, however web.whatsapp don't recognize it as an up-to-date browser. At the beginning an injector was used to avoid those warnings and bypass them. But that script is not working anymore. However you can use what saulocastelo said in order to maintain rhe configuration:

Pressing ctrl+shift+i (on Linux) and the Devtools window will open. Then click on Application -> Service Workers And check the option Bypass for network.

Now press ctrl+r to reload. And ctrl+shift+i to close the Devtools.

Whenever you open your whatsapp the problem will occur, but since the Bypass for network option has already been enabled, you only need to press ctrl+shift+i (open devtools), ctrl+r (reload), ctrl+shift+i (close devtools)

I dared to click on "WhatsApp is outdated, click here to update" today. In the past this did something what to my didn't change anything but today I got a screen "Update your browser" (which if clicked, opens the systems default browser). Restarting doesn't bring back the normal view, only deleting the profile and setting the app up from scratch. What exactly is "outdated"? How to suppress that warning and link? How to revert from that screen without losing all config?

@frealgagu the system tray owns to polybar

@jfernandz what Desktop Environment are you using?