-
Notifications
You must be signed in to change notification settings - Fork 30
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
whatsapp tray stopped working with the new store version of whatsapp. #143
Comments
What is the version exactly? |
I had the same problem since the 22H2 update. Went to the WhatsappTray installation folder and found this in the log files a lot: "07:45:53.388 - WhatsappTray::StartWhatsapp: WhatsApp-Window not found yet after 1000ms. Continue waiting ..." Opened 'appData.ini' and manualy launched the WhatsApp app as stated under "WHATSAPP_STARTPATH". So now the WhatsApp app was up to date and I manualy copied the WhatsappTray application folder to another location, set the WHATSAPP_STARTPATH path to the my current user account, changed my shortcuts so it launches the copy of WhatsApp tray with the correct user path, and everything works fine now. Hope this help u a little. |
The problem is that WhatsApp store version doesn't have static location |
I have the same problem |
It has a static location.. *:\Users\username\AppData\Local\WhatsApp |
The Microsoft store version can't be found in this folder |
Okay i'm sorry, i was confused with the normal app. |
OK I can now confirm the issue as the new version 2.2240.2.0 has been rolled out to me. |
Wait how do you get the normal app? Their website only has link the microsoft store |
Got it here: https://web.whatsapp.com/desktop/windows/release/x64/WhatsAppSetup.exe |
Yeah same problem here. |
Same problem here :-( |
Is there any fix for this? |
Describe the bug
WhatsApp UWP STORE version isn't working with whatsapptray
To Reproduce
Steps to reproduce the behavior:
Expected behavior
work
Screenshots
Desktop (please complete the following information):
w11 22h2
Log file when the bug happend
It's store version
The text was updated successfully, but these errors were encountered: