Chrome Update error... too
Search Criteria
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: | |
| Submitter: | frealgagu |
| Maintainer: | frealgagu |
| Last Packager: | frealgagu |
| Votes: | 85 |
| Popularity: | 4.04 |
| First Submitted: | 2018-12-14 22:30 |
| Last Updated: | 2020-08-13 03:50 |
Dependencies (7)
- gtk3 (gtk3-donnatella, gtk3-cosy, gtk3-adwaita-3-32-git, gtk3-mushrooms, gtk3-typeahead, gtk3-git, gtk3-patched-filechooser-icon-view, gtk3-ubuntu, gtk3-classic)
- libxss
- nss (nss-hg)
- imagemagick (graphicsmagick-imagemagick-compat, imagemagick-git, imagemagick-full-git, imagemagick-no-hdri, imagemagick-fftw, imagemagick-full) (make)
- nodejs-nativefier (make)
- unzip (unzip-natspec, unzip-iconv) (make)
- libindicator-gtk3 (libindicator-gtk3-ubuntu) (optional)
Required by (1)
Sources (3)
asolopovas commented on 2020-10-19 21:10
timofonic commented on 2020-09-17 10:40
Chrome Update error...
capoeira commented on 2020-09-14 10:50
my "solution" for the Chrome update error is having this, QtWaw and Ferdi installed. Ferdi always works; I use it when the ther 2 fail at the same time
jc-aur commented on 2020-09-13 02:24
@MrAureliusR did you add the preload.js when you compiled the application? It is working fine for me right now
MrAureliusR commented on 2020-09-12 21:10
Having the same Google Chrome update error. I'm assuming the package maintainer just needs to make a few changes to the way the package is compiled, I'm sure it'll get resolved fairly soon.
syrenity commented on 2020-09-12 17:55
Got Chrome Upgrade error again, any way to fix it?
girxchin commented on 2020-09-10 23:44
Used to have that 49+ chrome update problem, but it was solved by itself. now i got two issues: 1. It freezes randomly, letting me watch his key prompt blinking but completely unusable. 2. no tray icon. (i3wm, polybar).
omertuc commented on 2020-09-09 18:50
Seems like the tray problems are due to Chromium (and thus Electron and thus Nativefier) dropping support for xembed tray. This support was restored downstream in Electron, starting from version 9.0.3.
However, this package is pinned on Electron version 9.0.2. If the maintainers could bump it to the latest version or just 9.0.3 it would fix the problem (at-least for me, the problem was i3 not having support for StatusNotifierItem. It also seems Polybar doesn't support them as well).
je-vv commented on 2020-09-09 18:09
It looks like whatsapp-nativefier-inject.js is failing on me again after upgrading nodejs-nativefier to 10.1.0, but I'm not sure if that's just a coincidence. So again, no connection, but the google chrome big message...
Alborto commented on 2020-09-09 06:43
I have the same issue of the try bar disappearing after the lock of the session on gnome. I used --electron-version 9.0.2 but it seems to not work anymore. Any fix?
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());