Arch Linux User Repository

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.whatsapp-nativefier/releases/

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());

Hello guys,

It is solved by the new update of this evening with a correct user-agent argument in his PKGBUILD file...

I did a clean install when I was asked to PKGBUILDs to edit?. I edit the PKGBUILD and change the user-agent from safari to firefox.

I was able to temporarily fix the "Safari needs update" problem by editing the PKGBUILD:

yay -S --editmenu whatsapp-nativefier And changing the --user-agent param to use a more recent Safari UA:

--user-agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 12_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.4 Safari/605.1.15"

This worked - Just missing the final \

Many thanks @TluTalk

@TiuTalk & @franciscocpg That worked for me...! Thanks

To all of those having the "Safari needs update" issue, I did the following and worked just fine:

1. Press Ctrl + Shift + i (on Linux) and the Devtools window will open.
2. Then click on Application -> Service Workers
3. Uncheck the option Bypass for network.
4. Ctrl + R (refresh)
5. Repeat but this time CHECK Bypass for network
6. Ctrl + R (refresh) one more time

TLDR; Toggle "Bypass for network" and refresh every time

I checked the repo and did this: "Switch user agent to "firefox", which selects the latest stable release of that browser (https://github.com/nativefier/nativefier/blob/HEAD/API.md#user-agent)"

This fixed the old version message!

@MALRAT great solution!

For me the problem was not solved by just rebuild the application with updated user agent string.

To finally fix it I needed to clear the application cache data.

Open whatsapp-nativefier app. Press Shift-Ctrl-I, go to the Application tab, Storage menu item, uncheck all the checkboxes except "Cache storage" and click "Clear site data" button. After this press Ctrl-F5.

The application is not loosing the login data and just reloads the UI and starts to work.

https://ibb.co/nQs5Kn6

So, oddly enough - I tried updating the user agent string on both my desktops. One it worked, other I still get the Safari 11+ needed when I restarted it. On that one, I then opened dev tools and did a refresh and... it opened fine. Maybe a local cache issue ?

In my /opt/whatsapp-nativefier/resources/app/nativefier.json file on Manjaro, I have:

"userAgent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.4 Safari/605.1.15"

And it's not working...

@TiuTalk solution worked for me, but remember you need to clean and build the previous installation.

I was able to temporarily fix the "Safari needs update" problem by editing the PKGBUILD:

yay -S --editmenu whatsapp-nativefier

And changing the --user-agent param to use a more recent Safari UA:

--user-agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 12_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.4 Safari/605.1.15"

I too have the safari needs update problem, I tried to rebuild the package with the latest nativefier but with no luck.

From today issue saying safari needs to be updates, im on manjaro linux.

https://i.imgur.com/tm9Vavu.png

Hello,

On Manjaro Linux, whatsapp-nativefier complain at launch with a white and green screen that it needs Safari 11+ to work.

(ctrl+shift+i, Application -> Service Workers And check the option Bypass for network, and ctrl+r are useless...)

Traceback in Konsole:

(whatsapp-nativefier:11640): Gtk-WARNING **: 00:47:53.870: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version
[11674:0614/004754.176746:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[11640:0614/004755.247930:ERROR:browser_main_loop.cc(269)] GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

Hello,

It stoped working on Endeavour OS, error says to update Safari or use another browser.

Here is the console log:

Fontconfig error: "/etc/fonts/local.conf", line 1: parsing XML declaration: '?>' expected

Fontconfig error: "/etc/fonts/local.conf", line 1: XML declaration not well-formed
onReady ERROR Error: ERR_FAILED (-2) loading 'https://web.whatsapp.com/'
    at rejectAndCleanup (node:electron/js2c/browser_init:161:7647)
    at EventEmitter.stopLoadingListener (node:electron/js2c/browser_init:161:8022)
    at EventEmitter.emit (node:events:390:28) {
  errno: -2,
  code: 'ERR_FAILED',
  url: 'https://web.whatsapp.com/'
}

@Barbarah72 have you tried to build it with latest version of nativefier?

I'm having this issue where the app crashes every time I get a new message. Any clues?

On my KDE desktop I don't a tray icon anymore since the last update. Reinstall didnt worked. silos-whatsapp worked.

Operating System: Manjaro Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.16.14-1-MANJARO (64-bit) Graphics Platform: X11

@titaniumbones have you tried in a web browser, this packages only uses electron as a wrapper for web.whatsapp, I don't think is something related to the package.

as of today's update, I can no no longer link to whatsapp using this build. The silo-whatsapp package works, so I assume there's some issue somewhere in this package. Whatsapp has had a major update so maybe something has changed in the validation code.

Since some weeks in KDE and Xfce, whatsapp-nativefier launch popup a dialog box with "Old build detected" as title and "This app was built a long time ago. Nativefier uses the Chrome browser (through electron), and it is insecure to keep using an old version of it. Please upgrade Nativefier and rebuild this app." as text in the box...

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

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

Not working anymore

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

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.

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

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"

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.

@HMlendea have you tried the saulocastelo approach?

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

Having a problem asking to update Chrome. Can't start the app anymore.

@aquilarubra try building in a clean chroot, it works that way for me. Alternatively you can download an already built package from here:

https://github.com/frealgagu/archlinux.whatsapp-nativefier/releases/

Please don't flag the package as outdated, the method "Bypass for network mentioned in the pinned comments should work to avoid the Google Chrome 60+ issue.

Doesn't build. Error: Failed to locate module "electron-context-menu"

The package build fails for me:

$ makepkg -si
...
==> Entering fakeroot environment...
==> Starting package()...
sed: can't read /tmp/whatsapp-nativefier/src//resources/app/lib/preload.js: No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

It works if I use print $8 instead of print $9 on lines 44 and 45 of PKGBUILD, or if I drop the awk completely and use just ls without -l. Why is ls -l used instead of just ls anyway? None of the extra info is utilized.

@tywyqu Application is shown in tray? that's the correct way to close the app.

App continues to work in background after force closing it. Any way to elegantly kill it?

My current state is that with the pinned workaround, I get a "Browser not supported" message, and without it, I get the update prompt ("WhatsApp works with Google Chrome 60+"). Does anybody have a solution for this?

@jaro3 what AUR helper are you using? it looks like an error caused in package nodejs-nativefier, not in this. Error is clear that yargs only supports nodejs greater than 12, so, you need to install a nodejs version accordingly.

doesn't build ;-;

Error: yargs supports a minimum Node.js version of 12. Read our version support policy: https://github.com/yargs/yargs#supported-nodejs-versions
    at Object.<anonymous> (/usr/lib/node_modules/nativefier/node_modules/yargs/build/index.cjs:1:55294)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/lib/node_modules/nativefier/node_modules/yargs/index.cjs:5:30)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
==> ERROR: A failure occurred in build().
    Aborting...

nodejs-nativefier 44.0.2-2 is installed

Hi, today I get a particular error: onReady ERROR Error: ERR_FAILED (-2) loading 'https://web.whatsapp.com/' at rejectAndCleanup (electron/js2c/browser_init.js:213:985) at Object.stopLoadingListener (electron/js2c/browser_init.js:213:1360) at Object.emit (events.js:315:20) { errno: -2, code: 'ERR_FAILED', url: 'https://web.whatsapp.com/' }

Someone know what can I do?

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?

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

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 =)

Isn't that security issue though?

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"?

@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/

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

Any news on the "Old build detected" issue?

Is there a way to enable the tray icon?

Edit:Seems to be fixed now.

If you remove the --browserwindow-options '{ "webPreferences": { "spellcheck": true } }' it works perfectly

Edit: After the latest update this method does not work anymore, the only way i managed to get it working was through the devtools method

On startup, whatsapp-nativefier now complains about "Old build detected. This app was built a long time ago."

EDIT: Made a PR to resolve that.

Any way to keep the same window size? at each start it resets

An easy workaround for the "What's App works with Google Chrome 60+" issue is to open Devtools panel (ctrl+shift+i) then follow these steps:

• click on Application -> Service Workers and check the option Bypass for network ( this step was described by @saulcastelo )

• then navigate to More tools > Network conditions and at User Agent uncheck "Select automatically" and choose another user agent from the list. (I am currently getting good results with the "Firefox -- Windows" option, but this might change at some point).

Now Ctrl+R and closing the developers tools (Ctrl+Shift+i).

Ctrl+shift+i then Ctrl+r is still required occasionally when all that is shown is a blank screen.

I am getting the following error as well:

"What's App works with Google Chrome 60+"

Workaround is to use the web client on any browser.

@nursoda nativefier uses electron as browser, however web.whatsapp don't recognize it as an up-to-date browser. At the beginning an injector was used to avoid those warnings and bypass them. But that script is not working anymore. However you can use what saulocastelo said in order to maintain rhe configuration:

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)

I dared to click on "WhatsApp is outdated, click here to update" today. In the past this did something what to my didn't change anything but today I got a screen "Update your browser" (which if clicked, opens the systems default browser). Restarting doesn't bring back the normal view, only deleting the profile and setting the app up from scratch. What exactly is "outdated"? How to suppress that warning and link? How to revert from that screen without losing all config?

@frealgagu the system tray owns to polybar

@jfernandz what Desktop Environment are you using?

I haven't got the system tray icon either, is there a way to enable it?

@syrenity yes, inject is not working always. Try to do what @saulicastelo suggest, I think is the best workaround until now. Once you have the service worker bypass for network you only have to Ctrl+Shift+I then Ctrl+R and finally Ctrl+Shift+I when error message appears.

If somebody finds a better solution, please let me know and I'll update the package.

Tried the version here, still getting the Chrome error :(

https://github.com/frealgagu/archlinux.whatsapp-nativefier/releases/

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.whatsapp-nativefier/releases/

The Chrome error appeared again and there is no tray icon (using XFCE). Now it demands a higher version of Chrome (version number 60)

I'm getting this error when trying to update

==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
/usr/local/bin/node: /usr/local/bin/node: cannot execute binary file
==> ERROR: A failure occurred in build().
Aborting...
error making: whatsapp-nativefier

Please, help me fix this?

Chrome Update error... too

Chrome Update error...

https://i.imgur.com/23FZmi5.png

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

@MrAureliusR did you add the preload.js when you compiled the application? It is working fine for me right now

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.

Got Chrome Upgrade error again, any way to fix it?

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).

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).

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...

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?

Yes, it looks like it happens when you lock your session on gnome

Anyone else having issues with the icon not appearing in the tray?

Broken again for me.

I solved the Google Chrome 49+ error with:
sudo ln -s /usr/bin/chromium /usr/bin/chrome
This in case you don't have Chrome, but Chromium, which I think is for most users.

@aarestu, where should one place that piece of code, so that it becomes persisten?

first time I get "WhatsApp works with Google Chrome 49+" on this and qtWaw at the same time

function recheck () {
        if (document.querySelector("a[href='https://support.google.com/chrome/answer/95414']")) {
                console.log("reload");
                navigator.serviceWorker.getRegistration().then((registration) => {
                        registration.unregister();
                        document.location.reload();
                });
        }
        setTimeout(recheck, 5000); // callback

}
recheck();

this workaround worked for me

Created a package to disable the tray in whatsapp-nativefier

https://aur.archlinux.org/packages/whatsapp-nativefier-notray-hook/

For some reason it looks like the whatsapp-nativefier-inject.js script doesn't do its job.

For now, this is a workaround:

• Press ctrl + shift + i
• Follow the instructions in the pinned comment OR Paste this in the console (these are the contents of the injected script):

if (document.querySelector("a[href='https://support.google.com/chrome/answer/95414']")) {
        navigator.serviceWorker.getRegistration().then((registration) => {
            registration.unregister();
            document.location.reload();
        });
    }

I can confirm the chrome update message.

I suspect some magic is needed to get this working again. After the last update (today) I get a notification that a chrome update is required.

"WhatsApp works with Google Chrome 49+" "To use WhatsApp, update Crome or use ..."

There's a message that says WhatsApp works with Google Chrome 49+

Build seems to fail with the following error:

ls: cannot access '/var/tmp/pamac-build-matejd/whatsapp-nativefier/src/07:15': No such file or directory

sed: can't read /var/tmp/pamac-build-matejd/whatsapp-nativefier/src/07:15/resources/app/lib/preload.js: No such file or directory

Weirldy enough, it seems to be building in folder that has the same name than current time?

EDIT: I've examined PKGBUILD and script seems to be parsing exactly eight column ot the ls -l output. This is fine in most cases, but in my system is joined into domain, so it has additional column next to user and group. So, 8th column is the current time, while 9th column is actually the name of the folder.

Hello, Since a recent update of whatsapp-nativefier, the text and avatars have gotten a lot bigger which is very ugly on a large screen. Is this normal? I am on Manjaro Linux 20.0.3 Xfce.

I second and extend Sgt_Skinner's request: I would like a method to disable the tray icon entirely.

Hi, I don't know if I should ask this here. Can you please add an option to close WhatsApp without having to right click the icon in the system tray?

I am having a problem in here:

When I fix the icon in the system tray with: --electron-version 9.0.2 \

the problem with Tray icon left click behavior problem arise, so I use the fix --electron-version 9.0.3 \ but icon dissappears again.

Any way of having these two issues solved?

Tray icon left click behavior won't work properly. To fix, this should be added to the nativefier command after --name line in the PKGBUILD: --electron-version 9.0.2 \

Hello.

I'm the maintainer of the package https://aur.archlinux.org/packages/whatsapp-nativefier-dark/. Just want to inform that I'm deprecating that package in favor of this one because now WhatsApp has released the option to use the dark theme. Just go to settings -> theme and choose the dark theme.

@bakgwailo I don't understand why the bug continues appearing to you. The fix in dark version you mentioned was adjusted also in this version two months before than the dark version (thanks to @The-Compiler).

https://aur.archlinux.org/cgit/aur.git/commit/?h=whatsapp-nativefier&id=800d8e355aafe722261ea074d987936b65102546

Please try to uninstall the package completely then removes the temporal files and verify that the folder /opt/whatsapp-nativefier/ is either empty or non-existent. Then install it again and check if the issue continues.

So, I think in the dark version they fixed the Chrome upgrade message in this commit:

https://aur.archlinux.org/cgit/aur.git/commit/?h=whatsapp-nativefier-dark&id=523a9bc0c10edf972ce537b74241e5c3d21b313e

I get it probably every day at this point, and have to go into dev tools and clear the cache/reload the page to get it working again (which almost always then requires a re-auth).

I still can't get notifications.

edit: its a nativefier problem. after build, doing 'sed -i "s/const newNotify =.*/const newNotify = function (title, opt) {/" YOUR_DIRECTORY/resources/app/lib/preload.js' fixes it. https://github.com/jiahaog/nativefier/issues/956

The tray icon disappears on GNOME after locking and unlocking the screen. See this issue on Github: https://github.com/jiahaog/nativefier/issues/945 There is a solution at the end of the page. This should be added to the nativefier command in the PKGBUILD: --electron-version 7.2.4

I was unable to build the package, as a source file was missing:

sed: can't read /home/q/AUR/whatsapp-nativefier/src/whats-app-linux-x64/resources/app/lib/preload.js: No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

Removing sed -i -e "/loglevel/d" "${srcdir}/${_folder}/resources/app/lib/preload.js" from the PKGBUILD fixed it for me.

Seems not to work now and asks to upgrade to Chrome 49.

I have the same problem as @sispus (on kde too) but on true Arch

would be great as mentioned by @bakgwailo to add spellcheck support in the build:

diff --git a/PKGBUILD b/PKGBUILD
index 59b8809..b8c7589 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -33,6 +33,7 @@ build() {
     --verbose \
     --single-instance \
     --tray \
+    --browserwindow-options '{ "webPreferences": { "spellcheck": true } }' \
     "https://web.${pkgname%-nativefier}.com"
 }

Also is there a way to autom. enable the local dictionaries? By default for me only en_US was listed in ~/.config/whatsapp-nativefier-d40211/Preferences?

Any chance we could get:

--browserwindow-options '{ "webPreferences": { "spellcheck": true } }' \

added into the package build? It enables spell checking now that it is supported in electron.

Same thing as @willspoke: there is no tray icon for whatsapp. Any suggestion?

In manjaro kde no notification is sent. also notifications configuration window is not listing it among the applications. Notification sound works. I have had libindicator-gtk3 already, for another application.

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());

in cinnamon you need to go to options, general and activate indicators compatibility. And yes there is no notifications.

@xavery: Do you also have something for the notifications, it doesn't show up (the notification) if I get a message. For my xfce desktop I use the following: xfce4-notifyd Notification service.

Im on cinnamon, and there is no tray icon.. what app indicator i need to install?

@xavery: Thanks that worked!

@XTREEMRAGE : newer Electron versions have switched to using the newer "AppIndicator" status bar. Install xfce4-statusnotifier-plugin from AUR and add it to your panel. The component itself is named "Status Notifier Plugin".

@frealgagu : perhaps a message prompting the users to install AppIndicator status bars in their DE/WMs at install time would be in order?

Since the last 2 updates, I don't have a tray icon anymore in my XFCE environment. It does not show, does someone know where I can dig into for XFCE 4.14?

@je-vv, good to know. I will look into this. Thankd you so much!

@willspoke, it used to show up on the legacy tray, but now it does on the now so called notification area on LXQt (it's like the modern tray) Not sure if somehow that affects legacy trays at all. I think it's a electron thing, since now Signal and whatsapp both changed from legacy tray to new notification area Assuming also you didn't change the default tray option to false (I have it set to start-in-tray).

I am using i3, and on previous versions of this package, I would normally see a tray icon for whatsapp, but it is not showing for me at the moment. Does anybody else have this issue?

@shadowed87 glad it works for you as well. And thanks to the maintainer for including this fix in the PKGBUILD.

@xavery this fix is magic! Finally it works all the times!

@je-vv As I said, I have no idea what disabling this module does. I assume that, at worst, the JavaScript console simply won't have debug messages which aren't relevant to users anyway. Personally, I'm putting this package on hold in my system until something breaks.

@xavery, what you suggested does work for me as well. It shows the chrome 49+ for a second or so (I'd guess it'll depend on the CPU), and then it connects to the phone as usual... Is it dangerous to get it integrated into the AUR PKGBUILD? Thanks !

Add this line at the end of build() in PKGBUILD :

sed -i -e '/loglevel/d' WhatsApp-linux-x64/resources/app/lib/preload.js

I have no idea about JavaScript or if this doesn't break something half-important, but the app seems to work for me now.

Well, I was not getting the "Whatsapp works with Google Chrome 49+" until after whatsapp-nativefier upgraded to 0.4.1307-1. Now I have to remove the whatsapp stuff under .config and recognize the application QR on the phone, each time I want to launch whatsapp-nativefier, otherwise I get the error, :( Has anyone found a work around?

@The-Compiler thanks, I've included the script you suggested @kaefert @ErkiDerLoony I've added unzip as a make dependency, althought is strange as I always build the package in a clean chroot.

I just saw the change to support multiple languages in whatsapp-nativefier-inject.js - perhaps a better workaround would be to check for something on the page which doesn't change between languages, e.g. the link to the Chromium help page? Here's what I did for my own project:

https://github.com/qutebrowser/qutebrowser/blob/master/qutebrowser/javascript/whatsapp_web_quirk.user.js

had the LICENSE error too, first I tried uncommenting the install LICENSE line, that made the installation run through but no binary got installed either.

Then I looked a bit deeper and found that some unzipping failed and saw the comment of @ErikDerLoony about unzip missing as a dependency. Added that and now the install worked fine and it could be started afterwards.

Yes, me too.

I get "WhatsApp works with Chrome 49+" only. Cleaning the app data and relogin helps at first, then the warning comes back.

For me, makepkg fails with:

install: cannot stat '/XXX/whatsapp-nativefier/pkg/whatsapp-nativefier/opt/whatsapp-nativefier/LICENSE': No such file or directory

Anyone know where to get the LICENSE from?

Thanks!

Great package, thanks! Just one comment: You are missing unzip as a build dependency. Otherwise the build will fail in a clean chroot.

I just installed this package, thanks for the build.

As many may have encountered this issue in many electron apps on Linux (or even Chrome/Chromium package) there is a way of disabling gpu acceleration (if needed).

Simply adds --disable-gpu flag.

I found the MR talking about it there.

I can confirm the wrong checksum. But even after ignoring it and building, I Just get "WhatsApp works with Chrome 49+"... Is the User Agent setting wrong?

With the new update the installation is failing for me because of an incorrect checksum hash for whatsapp-nativefier-inject.js.

I get a pixelated icon on Plank dock, can you fix it please? :)

Any chance for multi-language support? :)

Thanks @frealgagu all smooth and slick again ;-)

@hjr Please verify and let me know what is happenning. The PKGBUILD should be working for WhatsApp and whats-app binary names.

@frealgagu it is the makepkg not running. When I change the cp .. line to install the src/.. dump I get a package, but plasma does not find WhatsApp. It does run flawless when called from a commandline. Something chahged with the apps name like WhatsApp to whats-app and/or also with the installation path. Have not yet tracked all the occurencies to fix.

@ector @hjr do you have the last version of nodejs-natifier installed? I think the folder name changes according to the version of nativefier

same problem

App built to /tmp/yaourt-tmp-ettore/aur-whatsapp-nativefier/src/whats-app-linux-x64 ==> Entering fakeroot environment... ==> Starting package()... cp: cannot stat '/tmp/yaourt-tmp-ettore/aur-whatsapp-nativefier/src/WhatsApp-linux-*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

Since the update on 1-30 makepkg does not run successfully any more.

==> Start package()... cp: Call stat on '/home/hjr/.cache/pacaur/whatsapp-nativefier/src/WhatsApp-linux-*' is not possible: File or directory not found

And, yes, there is a file like "whats-app-linux-x64". The source tar ball changed and does not fit any more to the PKGBUILD. Can only be a tiny fix, but I am not sure how to best workaround it.

whatsapp-nativefier-inject.js is not multi-language. Please replace it with something like:

if (document.body.innerHTML.replace(/\n/g, ' ').search(/class="landing-title version-title"/i) !== -1) navigator.serviceWorker.getRegistration().then(function (r) { r.unregister(); document.location.reload() });

@deathye Remove --tray from PKGBUILD.

how to disable the tray?

Related to my last comment, if someone have the same problem,deleting the entire ~/.config/whats-app-nativefier-d52542 only works until the next restart. As a work around , search the "Service Worker" folder in your /home/.config/whats-app-nativefier-d52542 and change the write and execute permissions to none.

Today (or I've discover it today) appears a warning that forces you to install chrome 49+ or use any desktop version of whatsapp. In any case blocks this app.

@eugen-b

All right, that rids of the error, but doesn't solve it totally. "/opt/${pkgname}/whats-app" (on line 42) also doesn't exist. /opt/whatsapp-nativefier/WhatsApp, does however.

According to https://forum.manjaro.org/t/aur-whatsapp-fehler-bei-paketerstellung/121479/15 line 41 in PKGBUILD should be changed to cp -rL "${srcdir}/WhatsApp-linux-"* "${pkgdir}/opt/${pkgname}"

I'm getting an error during pkg() (from the first cp in the function):

==> Starting package()...
cp: cannot stat '/tmp/makepkg/whatsapp-nativefier/src/whats-app-linux-*': No such file ordirectory
==> ERROR: A failure occurred in package().
    Aborting...
Error making: whatsapp-nativefier

It is required to install libindicator-gtk3 to view the system tray icon (using the appIndicator-support plugin). Could you please add it as an optional dependency?

I also get the 'wrong chrome version' warning when I start WhatsApp. I've worked around by pressing CTRL+SHIFT+I to open the chrome developer console and execute the following javascript

navigator.serviceWorker.getRegistration().then(r => { r.unregister(); document.location.reload() });

I have the same problem as @wyre stated below. whatsapp detects a "wrong chrome version" but after deleting ~/.config/whats-app-nativefier-d52542/ and reconnecting whatsapp web, it works again until the next restart.

I have to delete ~/.config/whats-app-nativefier-d52542/ every time I start whatsapp. Why is happening that? Could be fixed?

Hello dixi_minga,

It is only when Whatsapp is maximized before closing the app that it open in a window at the next launch (it is the same with Signal since last update of electron) and it could be an electron bug.

I'm on latest Manjaro Xfce stable.

@Armag67: thanks for the reminder

but for me it works: {"name":"whats-app",..,"tray":"start-in-tray",...,"darwinDarkModeSupport":false}

sudo chown root chrome-sandbox
chmod 4755 chrome-sandbox

Hello,

With today upgrade, /opt/whatsapp-nativefier/resources/app/nativefier.json change from "tray":false (or "tray":true) to "tray":"start-in-tray" does not work anymore, Whatsapp always opens in window or in full screen, but not in systray only.

why are you installing the files with 755 permission. why should those files have execute permission?

It does not work anymore because whatsapp web shows a wrong chrome version error when launching whatsapp-nativefier.

Looks like the nativefier build command is outdated. People on GitHub got it working again by adding --clear-cache and using electron version 6.0.9 (-e).

@frealgagu could you please update the PKGBUILD script? Thanks a lot!

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)

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.

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

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]

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

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.

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.

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

@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?

@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)

BTW, according to nativefier-api-tray, it's possible. However I applied whatsapp-nativefier --tray start-in-tray without any success... But looking at the PKGBUILD, it seems nativefier has to be called with the argument for --tray. Would it be possible to nativefy whatsapp with that?

Is there a way to start whatsapp-nativefier on tray (iconified on tray), like --start-in-tray? Is it possible to create a wrapper around whatsapp-nativefier to achieve that?

@frealgagu Thanks for the insight, guess I'll stick to browser WA Web for now until nativefier can support extensions.

EDIT: I've found a workaround! I exported the CSS code of my chosen Stylish styles and then injected it in a new nativefier.

@PF71 this package does not run over Chrome, it runs over electron, nativefier encapsulates electron pointing to a specified url. I don't think stylish works over electron, so I guess that what you suggest is not possible.

Please visit https://github.com/jiahaog/nativefier and you will have an idea of how nativiefier works.

@frealgagu Thanks for creating this package, it makes life easier by not having to open a browser tab for WA Web.

However, I like to use WA Web on Firefox using themes/skins or other CSS customizations from Stylish (https://userstyles.org/). Is there any way a Stylish extension can be used on whatsapp-nativefier like on a browser?

Another question, would you consider making a nativefier that runs on Mozilla's Gecko engine instead of Chrome?

@saulocastelo The fix is working. Thanks for your collaboration.

@benelexau fixed. Just wait the next update.

@freaigagu just change

if (document.body.innerText.replace(/\n/g, ' ').search(/whatsapp works with.to use whatsapp.update/i) === 0)

to

if (document.body.innerText.replace(/\n/g, ' ').search(/whatsapp works with.to use whatsapp.update/i) !== -1)

Live long and prosper!

@fxhm It works, thanks!

@mark I had the same issue. Scroll a bit down and take a look at the solutions: "rm -rf ~/.config/whats-app-nativefier-*"

After the latest whatsapp update it states "WhatsApp works with Google Chrome 36+", the same error what urged me to use this package.

I've updated all other packages, what else should I try?

Hi @saulocastelo off course. I had given the credits to @Frikinux who had provided the solution in a comment on December. I hadn't visited the bug thread in github and even noticed you had created the solution for this. Thank you. It helps a lot to not keep removing and reconfiguring each time that application starts.

Hi, @benalexau I'm the fix author. I will see this, soon as possible. The bug thread https://github.com/jiahaog/nativefier/issues/719

@frealgagu please, next package give the credits.

@gambas It's strange, try removing the folder ~/.config/whats-app-nativifier-* and reinstalling the package.

the systray icon have disappeared for me? it's blank instead. using plasma manjaro

@Freso I have no idea how to remove the notification about the update available. If anyone knows how to remove it, please let me know. Don't flag the package as out of date for this reason.

@frealgagu, I resolved my issue via "rm -rf ~/.config/whats-app-nativefier-*"

To minimize the application Ctrl+W can be used, but would it be possible to add a shortcut to close the window without minimizing it (e.g. Ctrl+Q)? I'm not familiar with nativefier, so not sure if this is possible or not.

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

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

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().

@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!

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

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.

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

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

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.

@ 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/

I get an "update available" message every time I start the program, even when rebuilding the package.

@Exeleration-G Nativefier creates an embeeded application so it's not possible to remove the tray once the application is created. If you want to remove the tray icon you need to remove the --tray line in PKGBUILD before execute makepkg (or edit it with your AUR helper if it has the capability).

I dislike the tray icon. Any way to make it minimize like a normal application?

@bionade24 Unfortunately whatsapp-web-desktop is not working and @tembleking has not attended, so this is an alternative, possibly we could merge but meanwhile this package will contain the necessary fix to work.

Why have you made new one instead of contributing to the existing whatsapp-web-desktop package?

It's strange, I'm using KDE Plasma also and the icon is shown OK. I'll try to add more icon sizes this weekend to see of it solves those issues.

Thanks for this. I use KDE-Plasma and my system-tray icon is completly oversized, like i only see a green square. Has someone a way to fix this?

@rplanchuelo I don't know how to achieve this with nativefier, the version in electron made in https://github.com/Enrico204/Whatsapp-Desktop which contain those features was abandoned.

Thanks. It's great. It would be interesting to include all the options of "new message" notifications (red dot in system tray icon)

I've created a package which include the fix for whatsapp using nativefier. Also I've added the icon from the webpage https://www.whatsapp.com/favicon.png and added the option to use in tray. Thanks @Frikinux for your collaboration.

https://aur.archlinux.org/packages/whatsapp-nativefier/

On the other hand, to make it more user-friendly, it is possible to add the option to start (and use it) minimized in the system tray.

Once installed, edit the file:

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

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

I recommend changing or editing too /opt/whatsapp-web/resources/app/icon.png with an image editor (like GIMP) to make the white background transparent (in format png).

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

The above can be added before installing in PKGBUILD as nativefier option: --tray "start-in-tray" \

I hope that helps. Greetings!

Hi! I've created a quick-fix based on nativefier injection (mentioned in https://github.com/jiahaog/nativefier/issues/719) for "WhatsApp works with Google Chrome 36+" error.

The error will disappear and the fix will survive at each start.

Create a archive named: inject.js

With the following content:

if (document.body.innerText.replace(/\n/g, ' ').search(/whatsapp works with.*to use whatsapp.*update/i) === 0)
    navigator.serviceWorker.getRegistration().then(function (r) { r.unregister(); document.location.reload() });

Save it in /opt/whatsapp-web/resources/app/inject/ folder.

The complete file path is therefore: /opt/whatsapp-web/resources/app/inject/inject.js

I hope it helps. Maybe it would be interesting to include it in the PKGBUILD for next versions. Enjoy it!

It seems related to nodejs-nativefier (https://github.com/jiahaog/nativefier/issues/719)

We must flag the package, then.

Seems that workaround, only works once. Then one needs to delete that dir everytime and relink the phone...

just rm -rf .config/whats*

WhatsApp desktop shows "WhatsApp works with Google Chrome 36+", maybe something related with nativefier or the version of electron appears to be an outdated Chrome?

@tembleking please add --tray to nativefier instruction in order to add the system tray icon. Thanks.

Is there any way to iconify the application? Something like other applications using electron. Thanks in advance.

I also can't reproduce the segfault

I cannot reproduce the segfault here.

On the other hand, the application name that appears in the task bar needs to be fixed.

Hi, it is possible to add a dark theme? through CSS or Electron or something else? Just like you change the style on browser with the addons "Stylus"

Thanks for your time. Best Regards

Is this compatible with any GNOME icon tray extension?

Impossible to download images

[BUG] impossible to download images from the desktop app

From the Arch GLIBC bug url:

https://bugs.archlinux.org/task/59550#comment171883

I installed a patched version of glibc and everything seems to work again:

pacman -U https://pkgbuild.com/~eschwartz/repo/x86_64/glibc-fix-r-and-electron-git-2.28.r24.g92a4cba760-1-x86_64.pkg.tar.xz

I tried with whatsapp, and Bitwarden (also eletron based and wasnt working before) and both work fine

It looks like there are several packages based on electron with the same issue. I've tried to install rocketchat-desktop but fails with "segmentation fault", however WhatsApp-web-desktop is working fine (I've not tried to reinstall it neither I want to do it). But it looks like is caused by glibc library once was upgraded to 2.28. With 2.27 it's working.

I'm having the same issue than @jhuesos

;-)

After last upgrade, I am getting:

/usr/bin/whatsapp-web-desktop: line 2: 21145 Segmentation fault

Same happens with Skype (which both use Electron). Strange thing is that Visual Studio Code (also electron) seems to work just fine.

I just tried to re-install whatsapp to see if that helped but nothing.

EDIT: I have tried to get more info about the issue (sorry, I am really a newbie on this) and after running:

LD_DEBUG=files whatsapp-web-desktop

I got a long output, but I guess this is the more relevant part:

  5580:     calling init: /opt/whatsapp-web/libnode.so
      5580:
/usr/bin/whatsapp-web-desktop: line 2:  5580 Segmentation fault      (core dumped) /opt/whatsapp-web/WhatsApp
      5579:
      5579:     calling fini: /bin/sh [0]

When I attempt to update, makepkg attempts to download a tarball from dropbox (https://www.dropbox.com/s/azeqhinhdwurn8s/WhatsApp-v0.5.0-linux-x64.tar.gz) - which fails.

I have cleaned the PKGBUILD a bit, if you want. I have kept only the sha256sums, removed dependency on another AUR package (nativefier), and replaced it with npm. Below is the patch:

diff --git a/PKGBUILD b/PKGBUILD
index 7fe574e..f04ff57 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -7,51 +6,43 @@ arch=('i686' 'x86_64')
 url="https://web.whatsapp.com"
 license=('unknown')
 depends=('alsa-lib' 'gconf' 'gtk2' 'libxss' 'libxtst' 'nss')
-makedepends=('nodejs-nativefier')
+makedepends=('npm')
 provides=('whatsapp-desktop')
 source=('whatsapp-web-desktop.png'
         'whatsapp-web-desktop.desktop'
-   'whatsapp-web-desktop.sh')
+        'whatsapp-web-desktop.sh')

 build() {
    cd $srcdir

-   nativefier web.whatsapp.com \
-       --name "whats-app" \
-       --disable-context-menu \
-       --disable-dev-tools \
-       --width 700px \
-       --height 700px \
-       -i "../$pkgname.png"
+  npm install nativefier
+   ./node_modules/.bin/nativefier web.whatsapp.com \
+    --name "whats-app" \
+    --disable-context-menu \
+    --disable-dev-tools \
+    --width 700px \
+    --height 700px \
+    -i "../$pkgname.png"

-   rm -rf whats-app
-   mv whats-app-* WhatsApp
-   mv WhatsApp/whats-app WhatsApp/WhatsApp
+  rm -rf whats-app
+  mv whats-app-* WhatsApp
+  mv WhatsApp/whats-app WhatsApp/WhatsApp
 }

 package() {
-   install -dm755 "$pkgdir/opt/whatsapp-web"
-   install -dm755 "$pkgdir/usr/bin/"
-   install -dm755 "$pkgdir/usr/share/pixmaps/"
-   install -dm755 "$pkgdir/usr/share/applications/"
+  install -dm755 "$pkgdir/opt/whatsapp-web"
+  install -dm755 "$pkgdir/usr/bin/"
+  install -dm755 "$pkgdir/usr/share/pixmaps/"
+  install -dm755 "$pkgdir/usr/share/applications/"

-   cp -R "$srcdir/WhatsApp/." "$pkgdir/opt/whatsapp-web/"
-   chmod 755 "$pkgdir/opt/whatsapp-web/resources/app"
+  cp -R "$srcdir/WhatsApp/." "$pkgdir/opt/whatsapp-web/"
+  chmod 755 "$pkgdir/opt/whatsapp-web/resources/app"

-   install -Dm755 "$srcdir/$pkgname.desktop" "$pkgdir/usr/share/applications/$pkgname.desktop"
-   install -Dm755 "$srcdir/$pkgname.png" "$pkgdir/usr/share/pixmaps/whatsapp.png"
-   install -Dm755 "$srcdir/$pkgname.sh" "$pkgdir/usr/bin/$pkgname"
+  install -Dm755 "$srcdir/$pkgname.desktop" "$pkgdir/usr/share/applications/$pkgname.desktop"
+  install -Dm755 "$srcdir/$pkgname.png" "$pkgdir/usr/share/pixmaps/whatsapp.png"
+  install -Dm755 "$srcdir/$pkgname.sh" "$pkgdir/usr/bin/$pkgname"
 }

-md5sums=('30ddc7f3e4c4acf46e698909fc8c37b6'
-         'b5b89ccd54a6e2ee7c8dfbaa21b223d5'
-         '78a9b5d6119cc5ccbc80df46c0c9d5ef')
-sha1sums=('47a4d26ed68125e77e7519c2a6c484d98b058ee2'
-          'eca6674f60349b59870ec098a7463258bc49ce8d'
-          'bff4262d17d6d13e7c5a0bea87960ebea3fc6189')
 sha256sums=('bf127917f50f8a4e4c9f217c7227cc0fe07783b186ae15d747f950f67ed9180d'
             'd08d57702dfcab2d3b37d7f3ef9a59955fe2432063fe5b6d91df999af609754b'
             'a3cb0c1c2f6f9fd574cdfc7e08814c3f7908bc4543ace8f3427d4636ddba9c29')
-sha512sums=('8e0c4742be68c7122eeb43c3b7318ceb3198f1a493798af51e27d11e92dea8f9dacf3a7ca39223da9ec017a6f476f3066cf62df7e2c3baacf72fb13d827c3706'
-            'a1c392b8a7a7045c3f955384be1eefb0ce51d781b656223ccbaffaeb939ba1fbebf4c4085fbc03f52bc24743208455cedc8f4e5b1d10e3885c150082bb585191'
-            '7c39adb302df5fbf5a222fd2ad623d348db0c6240069215f11547e072b96e65e363db5bd93d5a25075eab97c15567e89a3825d9b73fe9425e6176032e049c8a0')

I have tested on my laptop with makepkg --syncdeps --install --clean --cleanbuild --rmdeps and it is working properly. Please feel free to introduce the changes.

Your whatsapp package is not able to show the tray icon using this gnome extension

https://extensions.gnome.org/extension/615/appindicator-support/

Here the specific opened issue:

https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/130

EDIT: Apparently this is not the package which I've got installed, I've got installed whatsapp-desktop, but is not availabe at the day ... anyone has got more info? I would swear I've upgraded this whatsapp-desktop package recently

https://aur.archlinux.org/pkgbase/whatsapp-desktop/?comments=all

EDIT2: Ok, here is the explanation: https://github.com/Enrico204/Whatsapp-Desktop

Im sorry.

EDIT3: In any case, ... would you consider the suggestion about add system tray icon support? Thank you :-)