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());

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

@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.

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

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...

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.

whatsapp-nativefier-inject.js is not multi-language. Please replace it with something like:

if (document.body.innerHTML.replace(/\n/g, ' ').search(/class="landing-title version-title"/i) !== -1) navigator.serviceWorker.getRegistration().then(function (r) { r.unregister(); document.location.reload() });

@deathye Remove --tray from PKGBUILD.

how to disable the tray?

Related to my last comment, if someone have the same problem,deleting the entire ~/.config/whats-app-nativefier-d52542 only works until the next restart. As a work around , search the "Service Worker" folder in your /home/.config/whats-app-nativefier-d52542 and change the write and execute permissions to none.

Today (or I've discover it today) appears a warning that forces you to install chrome 49+ or use any desktop version of whatsapp. In any case blocks this app.