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 ... Next › Last »

xavery commented on 2020-03-25 20:54

Add this line at the end of build() in PKGBUILD :

sed -i -e '/loglevel/d' WhatsApp-linux-x64/resources/app/lib/preload.js

I have no idea about JavaScript or if this doesn't break something half-important, but the app seems to work for me now.

je-vv commented on 2020-03-25 20:24

Well, I was not getting the "Whatsapp works with Google Chrome 49+" until after whatsapp-nativefier upgraded to 0.4.1307-1. Now I have to remove the whatsapp stuff under .config and recognize the application QR on the phone, each time I want to launch whatsapp-nativefier, otherwise I get the error, :( Has anyone found a work around?

frealgagu commented on 2020-03-25 17:36

@The-Compiler thanks, I've included the script you suggested @kaefert @ErkiDerLoony I've added unzip as a make dependency, althought is strange as I always build the package in a clean chroot.

The-Compiler commented on 2020-03-24 18:29

I just saw the change to support multiple languages in whatsapp-nativefier-inject.js - perhaps a better workaround would be to check for something on the page which doesn't change between languages, e.g. the link to the Chromium help page? Here's what I did for my own project:

https://github.com/qutebrowser/qutebrowser/blob/master/qutebrowser/javascript/whatsapp_web_quirk.user.js

kaefert commented on 2020-03-22 15:00

had the LICENSE error too, first I tried uncommenting the install LICENSE line, that made the installation run through but no binary got installed either.

Then I looked a bit deeper and found that some unzipping failed and saw the comment of @ErikDerLoony about unzip missing as a dependency. Added that and now the install worked fine and it could be started afterwards.

HeinzDo1961 commented on 2020-03-20 13:24

Yes, me too.

sispus commented on 2020-03-20 11:00

I get "WhatsApp works with Chrome 49+" only. Cleaning the app data and relogin helps at first, then the warning comes back.

cvmd commented on 2020-03-18 18:30

For me, makepkg fails with:

install: cannot stat '/XXX/whatsapp-nativefier/pkg/whatsapp-nativefier/opt/whatsapp-nativefier/LICENSE': No such file or directory

Anyone know where to get the LICENSE from?

Thanks!

ErkiDerLoony commented on 2020-03-18 10:53

Great package, thanks! Just one comment: You are missing unzip as a build dependency. Otherwise the build will fail in a clean chroot.

Wattswing commented on 2020-03-14 09:53

I just installed this package, thanks for the build.

As many may have encountered this issue in many electron apps on Linux (or even Chrome/Chromium package) there is a way of disabling gpu acceleration (if needed).

Simply adds --disable-gpu flag.

I found the MR talking about it there.