Package Details: whatsapp-nativefier 2.2337.7-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: 135
Popularity: 1.02
First Submitted: 2018-12-14 22:30 (UTC)
Last Updated: 2023-09-08 19:25 (UTC)

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 26 Next › Last »

XAVeRY commented on 2023-05-26 20:41 (UTC)

Notifications seem to have stopped working at least in Xfce, detailed description here : https://github.com/frealgagu/archlinux.whatsapp-nativefier/issues/31

Lightning5 commented on 2023-04-01 12:55 (UTC)

@frealgagu thank you. I will ask there :)

peippo commented on 2023-03-28 07:21 (UTC)

Just got a temporary ban for using ’a third-party application’ - the only ‘unofficial’ thing I use is whatsapp-nativifier, which should look like any other web browser to WhatsApp, shouldn’t it?

frealgagu commented on 2023-02-01 21:11 (UTC)

@Lightning5 it's actually something to ask in https://github.com/nativefier/nativefier/

Lightning5 commented on 2023-01-22 19:10 (UTC)

Hi,

Is it possible to make this package respect flags in ~/.config/electron-flags.conf. This makes a huge difference for me as a Wayland user as, I don't have to add flags to desktop shortcuts to run WhatsApp in Wayland mode.

Armag67 commented on 2022-06-22 00:20 (UTC)

Hello guys,

It is solved by the new update of this evening with a correct user-agent argument in his PKGBUILD file...

dion_pouw commented on 2022-06-20 10:15 (UTC)

I did a clean install when I was asked to PKGBUILDs to edit?. I edit the PKGBUILD and change the user-agent from safari to firefox.

pentastarch commented on 2022-06-20 08:11 (UTC)

I was able to temporarily fix the "Safari needs update" problem by editing the PKGBUILD:

yay -S --editmenu whatsapp-nativefier And changing the --user-agent param to use a more recent Safari UA:

--user-agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 12_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.4 Safari/605.1.15"

This worked - Just missing the final \

Many thanks @TluTalk

Armag67 commented on 2022-06-18 19:25 (UTC)

@TiuTalk & @franciscocpg That worked for me...! Thanks

« First ‹ Previous 1 2 3 4 5 6 7 .. 26 Next › Last »