Package Details: whatsapp-nativefier 2.3000.1017392363-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: 136
Popularity: 1.29
First Submitted: 2018-12-14 22:30 (UTC)
Last Updated: 2024-10-16 17:54 (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 8 9 10 .. 26 Next › Last »

XTREEMRAGE commented on 2021-12-10 11:15 (UTC)

On my KDE desktop I don't a tray icon anymore since the last update. KDE plasma version 5.23.3 KDE framework version 5.88.0 Qt version 5.15.2

frealgagu commented on 2021-10-29 04:06 (UTC)

I've made some changes in whatsapp-nativefier-inject.js, could you test using the latest version of nodejs-nativefier?

lockeanarchist commented on 2021-10-12 21:30 (UTC)

Not working anymore

https://0x0.st/-I5H.png

Armag67 commented on 2021-10-03 22:53 (UTC) (edited on 2021-10-03 22:54 (UTC) by Armag67)

For launching whatsapp-nativefier only in tray (without window) I need after each update to use this old trick: Editing /opt/whatsapp-nativefier/resources/app/nativefier.json line "tray": true, to "tray": "start-in-tray", It's very useful when launching whatsapp-nativefier at logging. It could be pinned. Neither whatsapp-nativefier --start-in-tray neither whatsapp-nativefier --tray=start-in-tray are working.

frealgagu commented on 2021-09-30 22:08 (UTC)

Thanks, I've removed the conflicting line in PKGBUILD, please let me know how it works.

Nowaker commented on 2021-09-30 19:02 (UTC)

Update: this PKGBUILD has a line that breaks its injection code. Fix is in https://github.com/frealgagu/archlinux.whatsapp-nativefier/pull/11. Whoever builds it manually should get rid of this line:

  sed -i -e "/loglevel/d" "${srcdir}/${_folder}/resources/app/lib/preload.js"

Nowaker commented on 2021-09-29 00:28 (UTC) (edited on 2021-09-29 00:45 (UTC) by Nowaker)

Attention folks that get the error about Chrome being too old. Here's a dirty but 100% working workaround: https://github.com/frealgagu/archlinux.whatsapp-nativefier/issues/7#issuecomment-929708347

EDIT: I just realized the oneliner from @saulocastelo does exactly the same my 10 step guide does... So never mind. That said, I reported my findings to Nativefier as this appears to be a problem with Nativefier, not our JS inject code.

frealgagu commented on 2021-09-28 16:52 (UTC)

@HMlendea have you tried the saulocastelo approach?

lucasrizzini commented on 2021-09-28 00:19 (UTC) (edited on 2021-09-28 00:19 (UTC) by lucasrizzini)

@vikon, the answer for this issue is pinned here. Check saulocastelo's comment.