Package Details: whatsapp-nativefier 2.2245.9-1

Git Clone URL: (read-only, click to copy)
Package Base: whatsapp-nativefier
Description: WhatsApp desktop built with nativefier (electron)
Upstream URL:
Licenses: custom
Submitter: frealgagu
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 128
Popularity: 2.79
First Submitted: 2018-12-14 22:30 (UTC)
Last Updated: 2022-11-27 02:16 (UTC)

Pinned Comments

frealgagu commented on 2020-12-05 22:39 (UTC)

I maintain the latest built package at:

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='']") ), NICE/GREAT/GOOD!

Another way to do the same in 2 lines: document.querySelector("a[href='']") && navigator.serviceWorker.getRegistration().then(r => r.unregister() && document.location.reload());

Latest Comments

1 2 3 4 5 6 .. 25 Next › Last »

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

cmiranda commented on 2022-06-16 17:50 (UTC) (edited on 2022-06-16 17:52 (UTC) by cmiranda)

To all of those having the "Safari needs update" issue, I did the following and worked just fine:

  1. Press Ctrl + Shift + i (on Linux) and the Devtools window will open.
  2. Then click on Application -> Service Workers
  3. Uncheck the option Bypass for network.
  4. Ctrl + R (refresh)
  5. Repeat but this time CHECK Bypass for network
  6. Ctrl + R (refresh) one more time

TLDR; Toggle "Bypass for network" and refresh every time

yerasiito commented on 2022-06-16 16:41 (UTC)

I checked the repo and did this: "Switch user agent to "firefox", which selects the latest stable release of that browser ("

This fixed the old version message!

rickslash84 commented on 2022-06-16 08:41 (UTC)

@MALRAT great solution!

mallrat commented on 2022-06-16 06:36 (UTC) (edited on 2022-06-16 06:37 (UTC) by mallrat)

For me the problem was not solved by just rebuild the application with updated user agent string.

To finally fix it I needed to clear the application cache data.

Open whatsapp-nativefier app. Press Shift-Ctrl-I, go to the Application tab, Storage menu item, uncheck all the checkboxes except "Cache storage" and click "Clear site data" button. After this press Ctrl-F5.

The application is not loosing the login data and just reloads the UI and starts to work.

bakgwailo commented on 2022-06-16 02:18 (UTC)

So, oddly enough - I tried updating the user agent string on both my desktops. One it worked, other I still get the Safari 11+ needed when I restarted it. On that one, I then opened dev tools and did a refresh and... it opened fine. Maybe a local cache issue ?