Package Details: whatsapp-nativefier 2.2027.10-1

Git Clone URL: https://aur.archlinux.org/whatsapp-nativefier.git (read-only, click to copy)
Package Base: whatsapp-nativefier
Description: WhatsApp desktop built with nativefier (electron)
Upstream URL: https://web.whatsapp.com
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='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());

Latest Comments

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

thomas.oster commented on 2020-03-13 06:29

I can confirm the wrong checksum. But even after ignoring it and building, I Just get "WhatsApp works with Chrome 49+"... Is the User Agent setting wrong?

acxz commented on 2020-03-13 05:47

With the new update the installation is failing for me because of an incorrect checksum hash for whatsapp-nativefier-inject.js.

Alterego commented on 2020-02-24 15:46

I get a pixelated icon on Plank dock, can you fix it please? :)

Draghi commented on 2020-02-11 08:16

Any chance for multi-language support? :)

hjr commented on 2020-02-10 20:39

Thanks @frealgagu all smooth and slick again ;-)

frealgagu commented on 2020-02-10 15:50

@hjr Please verify and let me know what is happenning. The PKGBUILD should be working for WhatsApp and whats-app binary names.

hjr commented on 2020-02-09 10:43

@frealgagu it is the makepkg not running. When I change the cp .. line to install the src/.. dump I get a package, but plasma does not find WhatsApp. It does run flawless when called from a commandline. Something chahged with the apps name like WhatsApp to whats-app and/or also with the installation path. Have not yet tracked all the occurencies to fix.

frealgagu commented on 2020-02-08 16:35

@ector @hjr do you have the last version of nodejs-natifier installed? I think the folder name changes according to the version of nativefier

ector commented on 2020-02-08 14:26

same problem

App built to /tmp/yaourt-tmp-ettore/aur-whatsapp-nativefier/src/whats-app-linux-x64 ==> Entering fakeroot environment... ==> Starting package()... cp: cannot stat '/tmp/yaourt-tmp-ettore/aur-whatsapp-nativefier/src/WhatsApp-linux-*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

hjr commented on 2020-02-07 20:53

Since the update on 1-30 makepkg does not run successfully any more.

==> Start package()... cp: Call stat on '/home/hjr/.cache/pacaur/whatsapp-nativefier/src/WhatsApp-linux-*' is not possible: File or directory not found

And, yes, there is a file like "whats-app-linux-x64". The source tar ball changed and does not fit any more to the PKGBUILD. Can only be a tiny fix, but I am not sure how to best workaround it.