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.49
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 ... 6 7 8 9 10 11 12 13 14 15 16 ... Next › Last »

je-vv commented on 2019-05-12 00:03

BTW, according to nativefier-api-tray, it's possible. However I applied whatsapp-nativefier --tray start-in-tray without any success... But looking at the PKGBUILD, it seems nativefier has to be called with the argument for --tray. Would it be possible to nativefy whatsapp with that?

je-vv commented on 2019-05-11 23:58

Is there a way to start whatsapp-nativefier on tray (iconified on tray), like --start-in-tray? Is it possible to create a wrapper around whatsapp-nativefier to achieve that?

PF71 commented on 2019-04-15 12:50

@frealgagu Thanks for the insight, guess I'll stick to browser WA Web for now until nativefier can support extensions.

EDIT: I've found a workaround! I exported the CSS code of my chosen Stylish styles and then injected it in a new nativefier.

frealgagu commented on 2019-04-15 04:25

@PF71 this package does not run over Chrome, it runs over electron, nativefier encapsulates electron pointing to a specified url. I don't think stylish works over electron, so I guess that what you suggest is not possible.

Please visit and you will have an idea of how nativiefier works.

PF71 commented on 2019-04-14 23:56

@frealgagu Thanks for creating this package, it makes life easier by not having to open a browser tab for WA Web.

However, I like to use WA Web on Firefox using themes/skins or other CSS customizations from Stylish ( Is there any way a Stylish extension can be used on whatsapp-nativefier like on a browser?

Another question, would you consider making a nativefier that runs on Mozilla's Gecko engine instead of Chrome?

frealgagu commented on 2019-04-13 21:05

@saulocastelo The fix is working. Thanks for your collaboration.

saulocastelo commented on 2019-04-12 21:57

@benelexau fixed. Just wait the next update.

@freaigagu just change

if (document.body.innerText.replace(/\n/g, ' ').search(/whatsapp works use whatsapp.update/i) === 0)


if (document.body.innerText.replace(/\n/g, ' ').search(/whatsapp works use whatsapp.update/i) !== -1)

Live long and prosper!

mark commented on 2019-04-12 15:13

@fxhm It works, thanks!

fxhm commented on 2019-04-12 08:13

@mark I had the same issue. Scroll a bit down and take a look at the solutions: "rm -rf ~/.config/whats-app-nativefier-*"

mark commented on 2019-04-11 17:43

After the latest whatsapp update it states "WhatsApp works with Google Chrome 36+", the same error what urged me to use this package.

I've updated all other packages, what else should I try?