Yes, me too.
Search Criteria
Package Details: whatsapp-nativefier 2.3000.1017392363-1
Package Actions
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: | 135 |
Popularity: | 1.14 |
First Submitted: | 2018-12-14 22:30 (UTC) |
Last Updated: | 2024-10-16 17:54 (UTC) |
Dependencies (7)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libxss
- nss (nss-hgAUR)
- imagemagick (imagemagick-gitAUR, imagemagick-full-gitAUR, imagemagick-fullAUR) (make)
- nodejs-nativefierAUR (make)
- unzip (unzip-natspecAUR, unzip-zstdAUR) (make)
- libindicator-gtk3 (optional)
Required by (5)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 26 Next › Last »
<deleted-account> commented on 2020-03-20 13:24 (UTC)
sispus commented on 2020-03-20 11:00 (UTC)
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 (UTC) (edited on 2020-03-18 18:30 (UTC) by cvmd)
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 (UTC)
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 (UTC) (edited on 2020-03-14 09:58 (UTC) by Wattswing)
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.
thomas.oster commented on 2020-03-13 06:29 (UTC)
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 (UTC)
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 (UTC)
I get a pixelated icon on Plank dock, can you fix it please? :)
Draghi commented on 2020-02-11 08:16 (UTC)
Any chance for multi-language support? :)
hjr commented on 2020-02-10 20:39 (UTC)
Thanks @frealgagu all smooth and slick again ;-)
Pinned Comments
matejdro commented on 2023-10-06 04:51 (UTC)
Warning to all existing users: Nativefier is now unmaintained (https://github.com/nativefier/nativefier/issues/1577)
frealgagu commented on 2020-12-05 22:39 (UTC)
I maintain the latest built package at:
https://github.com/frealgagu/archlinux.whatsapp-nativefier/releases/
saulocastelo commented on 2020-03-29 10:46 (UTC)
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());