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: 135
Popularity: 1.07
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 11 12 .. 26 Next › Last »

awilliamson commented on 2021-06-25 18:36 (UTC)

As of 2.2121.6-1 I now get 'Unsupported Browser'. This was the change which set the browser agent to Safari. "Bypass for Network" fix from previous issues doesn't fix this one. Any suggestions?

Cantello commented on 2021-06-21 14:01 (UTC)

Thanks for this package! Any way to get unread badges on KDE?

Destac commented on 2021-06-10 15:52 (UTC)

I've signed up just to thank this fucking wonderful community.

Thank you very much for finding the solution to "What's App works with Google Chrome 60+"

@nate_x thanks to you I solved it. Thank you very much =)

matejdro commented on 2021-06-02 11:51 (UTC)

Isn't that security issue though?

rien333 commented on 2021-05-29 15:35 (UTC) (edited on 2021-05-29 15:48 (UTC) by rien333)

The spellchecking capability is nice, but does anyone know if there's option to change the language somehow?

EDIT: See documentation. Perhaps it would be possible to insert this into whatsapp-nativefier-inject.js, and then check what lanuages someone is using at "build-time"?

frealgagu commented on 2021-05-16 13:53 (UTC)

@ector try cleaning the yay cache folder, if problem persists, try removing the user npm folder. If none of those helps you, you have two options, make a clean chroot compilation or download the generated package from https://github.com/frealgagu/archlinux.whatsapp-nativefier/releases/

ector commented on 2021-05-16 09:26 (UTC) (edited on 2021-05-16 09:30 (UTC) by ector)

Hi,have this errors whit yay

at Module._compile (node:internal/modules/cjs/loader:1109:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10) ==> ERROR: A failure occurred in build().

Thank

Cheers

jrabensc commented on 2021-05-06 05:33 (UTC)

Any news on the "Old build detected" issue?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 26 Next › Last »