@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.
Search Criteria
Package Details: whatsapp-nativefier 2.2337.7-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: | 134 |
| Popularity: | 0.166119 |
| First Submitted: | 2018-12-14 22:30 (UTC) |
| Last Updated: | 2023-09-08 19:25 (UTC) |
Dependencies (7)
- gtk3 (gtk3-ubuntuAUR, gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR, gtk3-classicAUR)
- 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 (4)
Sources (3)
hjr commented on 2020-02-09 10:43 (UTC)
frealgagu commented on 2020-02-08 16:35 (UTC)
@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 (UTC)
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 (UTC)
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.
Draghi commented on 2020-02-02 12:42 (UTC) (edited on 2020-02-12 14:54 (UTC) by Draghi)
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.
lockeanarchist commented on 2020-02-01 16:56 (UTC)
how to disable the tray?
zuzavo commented on 2020-01-29 13:53 (UTC) (edited on 2020-01-29 18:13 (UTC) by zuzavo)
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.
zuzavo commented on 2020-01-29 03:57 (UTC) (edited on 2020-01-29 04:08 (UTC) by zuzavo)
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.
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());