search

mimbrero / whatsapp-desktop-linux

Unofficial WhatsApp Linux client built with Electron.
https://flathub.org/apps/details/io.github.mimbrero.WhatsAppDesktop
MIT License
79 stars 20 forks source link

"WhatsApp works with Chrome 60+" #45

Open JGMelon22 opened 1 year ago

JGMelon22 commented 1 year ago

Every now and then it's show the title error, a workaround is to delete ~/.var/app/io.github.mimbrero.WhatsAppDesktop. Maybe bump electron version will help? image Cordially: JG

Razer0123 commented 1 year ago

Same issue, can't use the app anymore since today

JGMelon22 commented 1 year ago

Same issue, can't use the app anymore since today

Did you try the palliative repair I've previous mentioned?

duffxp commented 1 year ago

@JGMelon22 , thank you! It worked well.

Just out of curiosity: why does deleting all directories (cache and config) help?

JGMelon22 commented 1 year ago

@JGMelon22 , thank you! It worked well.

Just out of curiosity: why does deleting all directories (cache and config) help?

I can't say for sure, but I reckon delete the flatpak program cache data and "by passes" the WhatsApp web requirement for a newer chromium browser version

Plarpoon commented 1 year ago

After over two months the issue still presents itself, I do think a bump of the Chromium version should permanently get rid of the issue

mimbrero commented 1 year ago

Hello, this bug is showing up since the first version of the app. I'm afraid that this has actually nothing to do with the user agent or the chromium/electron version. That's why deleting the application data or usually just reloading the app (Ctrl+R) solves the issue.

As fas as I know, this is somehow Facebook's fault. They just send this error whenever they want and, as I mentioned, it has nothing to do with any version. Maybe it's an electron issue and the app handles it this way, if you want to be well-thought, but I think this is some way that they have to break unofficial clients.

I tried to fix this by forcing to reload the webpage whenever the "wrong version" banner is detected, because some days after installing the app, it was unusable for everybody as the banner was always showing. Apparently, following the implementation of this fix, it was working for everybody but the participants in this issue.

A friend of mine also ran into this but, when I asked him to test something, it was magically solved. Has this happened to you by chance? Is all working now?

JGMelon22 commented 1 year ago

I tried to fix this by forcing to reload the webpage whenever the "wrong version" banner is detected, because some days after installing the app, it was unusable for everybody as the banner was always showing. Apparently, following the implementation of this fix, it was working for everybody but the participants in this issue.

A friend of mine also ran into this but, when I asked him to test something, it was magically solved. Has this happened to you by chance? Is all working now?

I think I do remember this problem, even with others unofficial WhatsApp desktop clients for Linux were having... After your better explanation why this "quirky" happens, the only thing I may say is FU Meta/Facebook... By the way, any chances to at least one in a while have an electron bumped to newer versions? Thanks for supporting the community, mimbrero 🙋🚀

tuganetworks commented 9 months ago

I not have "app" after var/

JGMelon22 commented 9 months ago

I not have "app" after var/

Because the correct directory is .var