Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug Report] Whatsapp works with Chrome 60+ #172

Closed
asarubbo opened this issue Mar 17, 2022 · 5 comments
Closed

[Bug Report] Whatsapp works with Chrome 60+ #172

asarubbo opened this issue Mar 17, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@asarubbo
Copy link

Describe the bug
After closing and reopening WALC I get:
Screenshot_20220317_115205

I can bypass the issue by removing $HOME/.config/walc and logging in again with the QR code

WALC Installation Type:
git clone / npm install

Did you try closing and then opening it back?: Yes

System Information (please complete the following information):

  • OS/Distro: Gentoo
@asarubbo asarubbo added the bug Something isn't working label Mar 17, 2022
@Zzombiee2361
Copy link
Collaborator

We actually have a system in place to get past this. But we're checking if you're stuck in this page by searching the string "Update Google Chrome", so currently it only works in english. I'm gonna add a more robust checking system soon!

You could switch your system language to english as a workaround for now.

@lashkevi
Copy link

lashkevi commented Jun 2, 2022

The same problem with the new version of the WhatsApp application independently of the system language. The output is attached
walc.log
.

@BenHerbst
Copy link

I have the issue today

@Zzombiee2361
Copy link
Collaborator

Please try the new beta version https://github.com/WAClient/WALC/releases/tag/v0.3.0-beta.0

@Sadi58
Copy link

Sadi58 commented Dec 22, 2022

I've tried the latest Beta, which made no difference. So I returned to "WALC-0.2.4.AppImage", and today I don't see this message during the usual updating process.
Probably it was due to an upstream bug, which has been fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants