Package Details: whatsapp-nativefier 2.2033.7-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: 85
Popularity: 6.03
First Submitted: 2018-12-14 22:30
Last Updated: 2020-08-13 03:50

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

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

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.

vmsh0 commented on 2020-07-22 18:36

I second and extend Sgt_Skinner's request: I would like a method to disable the tray icon entirely.

Sgt_Skinner commented on 2020-07-17 17:20

Hi, I don't know if I should ask this here. Can you please add an option to close WhatsApp without having to right click the icon in the system tray?

mac_arch commented on 2020-07-10 16:12

I am having a problem in here:

When I fix the icon in the system tray with: --electron-version 9.0.2 \

the problem with Tray icon left click behavior problem arise, so I use the fix --electron-version 9.0.3 \ but icon dissappears again.

Any way of having these two issues solved?

sispus commented on 2020-07-08 16:44

Tray icon left click behavior won't work properly. To fix, this should be added to the nativefier command after --name line in the PKGBUILD: --electron-version 9.0.2 \

franciscocpg commented on 2020-07-08 14:39


I'm the maintainer of the package Just want to inform that I'm deprecating that package in favor of this one because now WhatsApp has released the option to use the dark theme. Just go to settings -> theme and choose the dark theme.

frealgagu commented on 2020-06-19 15:57

@bakgwailo I don't understand why the bug continues appearing to you. The fix in dark version you mentioned was adjusted also in this version two months before than the dark version (thanks to @The-Compiler).

Please try to uninstall the package completely then removes the temporal files and verify that the folder /opt/whatsapp-nativefier/ is either empty or non-existent. Then install it again and check if the issue continues.

bakgwailo commented on 2020-06-19 04:31

So, I think in the dark version they fixed the Chrome upgrade message in this commit:

I get it probably every day at this point, and have to go into dev tools and clear the cache/reload the page to get it working again (which almost always then requires a re-auth).