altus
altus copied to clipboard
amanharwara
WhatsApp works with Google Chrome 60+, update Google Chrome
Can't use Altus 4.5.3 anymore since this morning.
A message pops up to update to the latest Google Chrome version. I've tried updating my local Google Chrome but I don't think it's connected. Force reloading doesn't fix the problem either.
Please use 4.5.2 for the time being. I'm aware of what's causing this, but can't roll out a fix yet
Could you test this? https://github.com/amanharwara/altus/releases/tag/4.5.4
Unfortunately it doesn't work. The problem with the "update to the latest Google Chrome" does go away, but now the issue is that the fix in issue https://github.com/amanharwara/altus/issues/159 seems reverted.
So I see "Connecting to WhatsApp" message again after using 4.5.4. Force reloading doesn't work. Multiple restarts of Altus also didn't work.
Let me know if you want me to test anything else! I've got all day today haha
The trouble I'm having with this is that the fix for the "Update Chrome" thing is what causes the Multi-device beta to stop working, and vice-versa.
Ok, well I just checked. This is indeed working when I disable the Multi-device beta again. So for now, this works for me :) Thanks for all your support and effort! If you need me to test a new version again with the beta enabled, let me know!
Right now, to fix the "Update Chrome" error, Altus unregisters the service workers, and clears the WebSQL db and the IndexedDB attached to WhatsApp. Admittedly, I'm not sure if clearing all of that is required. If somebody can isolate what we need to clear/unregister to fix the "Update Chrome" error, then it might be possible to only remove that, and keep what's necessary for the Multi-device beta to work.
The 'Update Chrome' message pops up again for me in 4.5.4 after rebooting the pc. Closing the tab and creating a new one fixes it, but that means recreating the tab and settings on every boot...
The 'Update Chrome' message pops up again for me in 4.5.4 after rebooting the pc. Closing the tab and creating a new one fixes it, but that means recreating the tab and settings on every boot...
In that case right now, you'll need to downgrade to v4.5.2.
@RayneShall I had the same problem, but after clicking 'Clear cache' (under settings) and then 'Force reload' fixed the problem. It does however seem to be a temp fix. After a couple of restarts, the 'Update Chrome' message does seem to pop up again. But simply follow above steps again to fix it again!
@amanharwara Maybe the fix should be to automatically clear cache each time Altus boots? Not entirely sure, but could be a possible fix for this problem.
Clear Cache + Force Reload definitely fixes it temporarily. That's a good enough workaround for now.
I'll keep 4.5.2 around just in case.
but after clicking 'Clear cache' (under settings) and then 'Force reload' fixed the problem.
@Fidelity88 After you did this, was the multi-device beta working for you?
but after clicking 'Clear cache' (under settings) and then 'Force reload' fixed the problem.
@Fidelity88 After you did this, was the multi-device beta working for you?
Haven't tried that yet. I was referring to the use of 'multi-device beta' as disabled.
But I've tested this now. The result is very weird... When I clear the cache and force reload. The notice as stated in my first comment (update to the latest Google Chrome version) is gone! So it seemed to work, but... WhatsApp doesn't load in. It stays on the 'Connecting to WhatsApp' screen for a long time.
Then after maybe 1 or 2 minutes have passed, it shows an error 'Connecting to WhatsApp, make sure your computer has an active internet connection'
So yes, the beta is working. But unusable. If I clear the cache, force reload etc. the same thing happens again. The only option I have is to click 'Log out' and disable the beta again.
This seems to be back with 4.7.4. And it does not only occur after a reboot, but also after suspend to ram. (Altus: 4.7.4 Electron: 20.0.3 Chrome: 104.0.5112.81 V8: 10.4.132.20-electron.0 OS: Windows_NT x64 10.0.19044)
In 4.8.0 the message still appears, but cmd+r to reload fixes it. I can confirm that it appears after "suspend to ram". Any cleaner way to stop the message popping up completely?
I found the following resources on a similar project discussing the same problem: nativefier/nativefier#1112. They did come up with a solution similar to the one being used now.
But there seems to be a more robust way of fixing this. nativefier/nativefier#1312 is the suggested solution and nativefier/nativefier#1316 is the PR. Implementing nativefier/nativefier#1316 seems much cleaner than the current patchwork.
I found the following resources on a similar project discussing the same problem: nativefier/nativefier#1112. They did come up with a solution similar to the one being used now.
But there seems to be a more robust way of fixing this. nativefier/nativefier#1312 is the suggested solution and nativefier/nativefier#1316 is the PR. Implementing nativefier/nativefier#1316 seems much cleaner than the current patchwork.
Very interesting. Implemented this and it looks good on my side. Will put out a release with this soon.
Thank you very much!
Hey everyone, if you are still facing this issue, please try out the latest build v4.8.1 and let me know if that fixes it for you.