Package Details: whatsapp-nativefier 2.2033.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: 85
Popularity: 6.47
First Submitted: 2018-12-14 22:30
Last Updated: 2020-08-13 03:50

Pinned Comments

saulocastelo commented on 2020-03-29 10:46

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 ... 5 6 7 8 9 10 11 12 13 14 15 ... Next › Last »

jemadux commented on 2019-08-28 10:00

whatsapp-nativefier [21539:0828/125831.858706:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/whatsapp-nativefier/chrome-sandbox is owned by root and has mode 4755. Παγίδα Trace/breakpoint (core dumped)

Raketenjoint commented on 2019-08-20 07:17

When I play voice recordings, I do not get any sound. A sink pops up in pavucontrol but it does not have any volume. Notification sounds are played properly in comparison.

frealgagu commented on 2019-08-04 02:11

@yoburtu Try to use makepkg directly and tell me what happens.

yoburtu commented on 2019-07-03 08:56

The package can't be created:

/tmp/yaourt-tmp-user/aur-whatsapp-nativefier/./PKGBUILD: line 44: 19177 Aborted (core dumped) convert "${srcdir}/${pkgname}.png" -resize "${_size}" "${pkgdir}/usr/share/icons/hicolor/${_size}/apps/${pkgname}.png" ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build whatsapp-nativefier. ==> Restart building whatsapp-nativefier ? [y/N]

Freso commented on 2019-05-28 19:34

Remember to bump $pkgrel when you edit the PKGBUILD—in a way that changes the resulting package—without increasing $pkgver

gargakumar commented on 2019-05-26 20:16

Hi this package is causing issues with some docks apps like plank (icon not showing properly). Package whatsapp-nativefier.desktop reads StartupWMClass=whatsapp-nativefier however window class reported by wmctrl is "whats-app-nativefier-d52542". This apparently confuses plank. Changing the *.desktop file to StartupWMClass=whats-app-nativefier-d52542 fixes temporarily the issue... until next AUR update. Is there a way to properly fix this ? Thanks.

Freso commented on 2019-05-13 09:55

I’d prefer if frealgagu doesn’t implement this, however, it is easy to clone a PKGBUILD and maintain it locally using git. Just git fetch and git merge when there’s an update on AUR. I do this for a couple of PKGBUILDs where I want to tweak the defaults.

Frikinux commented on 2019-05-13 07:10

@je-vv Yeap! The only way that I believe... it's that the Maintainer edit the PKGBUILD with this option.

je-vv commented on 2019-05-12 23:12

@Frikinux, sorry about that. I didn't remember about back then. Yes, I tried then, and I'm currently using the 1st option. I didn't like them back then because none of them is permanent, for the 1st one, I have to remember to modify the PKGBUILD when upgrading, and for the 2nd one, that json gets overwritten on upgrade as well (it gives the chance to edit it after the upgrade, but you still have to remember to do it).

Is there a way to have a ~/ config file overwriting just that parameter? Or, is there a way to make both options available through a wrapper applying the corresponding configuration? So far it's a configuration in a json file, I'm wondering if it might be an argument instead, that has precedence over the json file.

Any ways, I guess for you "start-in-tray" by default is not an option, right?

Frikinux commented on 2019-05-12 14:04

@je-vv On 2019-02-03 I answered this same question. Yes you can. You can not forget to put the quotes in the argument.

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)