Package Details: whatsapp-nativefier 2.2027.10-1

Git Clone URL: (read-only, click to copy)
Package Base: whatsapp-nativefier
Description: WhatsApp desktop built with nativefier (electron)
Upstream URL:
Licenses: custom
Submitter: frealgagu
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 77
Popularity: 4.34
First Submitted: 2018-12-14 22:30
Last Updated: 2020-07-08 19:49

Pinned Comments

saulocastelo commented on 2020-03-29 10:46

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='']") ), NICE/GREAT/GOOD!

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

Latest Comments

1 2 3 4 5 6 ... Next › Last »

je-vv commented on 2020-08-12 18:08

@aarestu, where should one place that piece of code?

capoeira commented on 2020-08-12 12:57

first time I get "WhatsApp works with Google Chrome 49+" on this and qtWaw at the same time

aarestu commented on 2020-08-12 03:33

function recheck () {
        if (document.querySelector("a[href='']")) {
                navigator.serviceWorker.getRegistration().then((registration) => {
        setTimeout(recheck, 5000); // callback


this workaround worked for me

deathye commented on 2020-08-12 02:34

Created a package to disable the tray in whatsapp-nativefier

omertuc commented on 2020-07-29 09:21

For some reason it looks like the whatsapp-nativefier-inject.js script doesn't do its job.

For now, this is a workaround:

  • Press ctrl + shift + i
  • Follow the instructions in the pinned comment OR Paste this in the console (these are the contents of the injected script):
if (document.querySelector("a[href='']")) {
        navigator.serviceWorker.getRegistration().then((registration) => {

irvelervel commented on 2020-07-29 07:22

I can confirm the chrome update message.

dries007 commented on 2020-07-29 07:13

I suspect some magic is needed to get this working again. After the last update (today) I get a notification that a chrome update is required.

"WhatsApp works with Google Chrome 49+" "To use WhatsApp, update Crome or use ..."

stefnix commented on 2020-07-29 00:26

There's a message that says WhatsApp works with Google Chrome 49+

matejdro commented on 2020-07-27 05:17

Build seems to fail with the following error:

ls: cannot access '/var/tmp/pamac-build-matejd/whatsapp-nativefier/src/07:15': No such file or directory

sed: can't read /var/tmp/pamac-build-matejd/whatsapp-nativefier/src/07:15/resources/app/lib/preload.js: No such file or directory

Weirldy enough, it seems to be building in folder that has the same name than current time?

EDIT: I've examined PKGBUILD and script seems to be parsing exactly eight column ot the ls -l output. This is fine in most cases, but in my system is joined into domain, so it has additional column next to user and group. So, 8th column is the current time, while 9th column is actually the name of the folder.

Armag67 commented on 2020-07-26 21:00

Hello, Since a recent update of whatsapp-nativefier, the text and avatars have gotten a lot bigger which is very ugly on a large screen. Is this normal? I am on Manjaro Linux 20.0.3 Xfce.