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.04
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 .. 17 18 19 20 21 22 23 24 25 26 Next › Last »

frealgagu commented on 2019-03-05 16:52 (UTC)

@benalexau It's strange, the whatsapp-nativefier-inject.js actually works as a workaround injecting a javascript to skip that validation.

benalexau commented on 2019-03-04 06:20 (UTC)

From a freshly built package I get, "WhatsApp works with Google Chrome 36+". Anyone else seen this or know a workaround?

nakednous commented on 2019-02-21 13:27 (UTC)

Hello, thanks for the package. I got this error:

$HOME/.cache/yay/whatsapp-nativefier/PKGBUILD: línea 41: 5613 Abortado (`core' generado) convert "${srcdir}/${pkgname}.png" -resize "${_size}" "${pkgdir}/usr/share/icons/hicolor/${_size}/apps/${pkgname}.png" ==> ERROR: Se produjo un fallo en package().

Frikinux commented on 2019-02-03 09:34 (UTC)

@je-vv It's possible to add the option to start (and use it) minimized in the system tray.

Before installing, modify in PKGBUILD as nativefier option: --tray "start-in-tray" \

Or... Once installed, edit the file:

/opt/whatsapp-nativefier/resources/app/nativefier.json

and change "tray":false for "tray":"start-in-tray" (with quotes)

It would be interesting to include all the options of "new message" notifications (red dot in system tray icon) in the version of https://github.com/Enrico204/Whatsapp-Desktop

I hope that helps. Greetings!

je-vv commented on 2019-02-03 01:29 (UTC)

Can the app start on tray without popping up at once?

frealgagu commented on 2019-02-01 21:50 (UTC)

I'm going to do the change, is somebody wants possibility to have more than one whats app web, he must change the package build and remove the --single-instance flag.

frealgagu commented on 2019-01-31 18:51 (UTC)

What about someone who wants to have several whats app accounts?

je-vv commented on 2019-01-31 00:14 (UTC)

+1 to @nit's comment on not bringing several instances up...

nit commented on 2019-01-27 22:50 (UTC)

It's probably a good idea to add the --single-instance flag to the build command.

https://github.com/jiahaog/nativefier/blob/master/docs/api.md#single-instance

Prevents application from being run multiple times. If such an attempt occurs the already running instance is brought to front.

frealgagu commented on 2019-01-17 14:13 (UTC)

@ Edootjuh It's something related to web client, sometimes the same happens in a browser: https://www.reddit.com/r/whatsapp/comments/4j5y7y/does_anybody_else_have_the_update_available_click/