Device unreachable. Not automatically reconnecting unlike WhatsApp Web and Signal Desktop
orschiro opened this issue · comments
Hey guys!
I have WhatsApp Web and Signal Desktop and both reconnect just fine.
However, Threema doesn't.
At some point (after airplane modes, standby/hibernation, reconnection of wifi, etc), it just shows me the device unreachable message without reconnecting by itself which WhatsApp Web and Signal Desktop can without any issues.
Is this a specific problem just on my end or are more people affected here?
On my Android, all these three apps have the exact same settings regarding battery optimisation, internet access, etc.
Also no difference for them on my laptop. They all run inside the same browser, except for Signal Desktop obviously, which is a separate app.
Any insights are appreciated, thanks!
Same for me (iOS user). Whereas I cannot recognize any pattern - it just disconnects from time to time (or shows a red bar on top instead of a green bar). F5, re-entering the pin and the app reloads. Bit annoying though.
WhatsApp used to be similar in the very early days of WhatsApp Web. Signal on the other hand has a completely different design and connects directly to the servers instead of going via your phone.
If you have already checked out the tipps at https://threema.ch/en/faq/web_reconnect and https://threema.ch/en/faq/web_connection_drop, I don't think there is much that you can do except to launch Threema on your phone and force the reconnect that way.
But Threema has announced a full desktop client (similarish to what Signal does) which should solve this particular issue once and for all. There is a blog post with some more information at https://threema.ch/en/blog/posts/md-architectural-overview-intro.
Samsung is the worst 🙂
Did you already check out https://dontkillmyapp.com/? You could also try installing their app to diagnose whether backup activity works or not.
@dbrgn good thinking!
Tried the app and the problem doesn't seem to come from my phone. 100% after 8 hours of testing:
DontKillMyApp Ergebnis
SM-A320FL (a3y17lte) by samsung, Android 8.0.0
TOTAL
100%
WORK
100%
MAIN
100%
ALARM
100%
DURATION
8:00:00
Are you familiar with the browser developer tools (F12)? You could also keep the network tab open. When Threema Web tries to wake up a device, you can observe the requests against the push server. If these are responded to with a HTTP 204 response code, that means that the push message was successfully delivered to the Google/FCM push server.
I think we should take a step back here. There is no retry button which would indicate that the desktop/notebook has connectivity issues and not the smartphone. Therefore, I'd classify it as a support case and recommend sending a log to *SUPPORT (Troubleshooting, next to About in the footer) once this happens.
@lgrahl just submitted!
From the log you've sent, we can see that there were a dozen of automatic reconnections, so it does mostly work as one would expect it to. At the very end of the log, sending of the push fails (I'm assuming due to connectivity issues/no network connection on the notebook) and that tripped the state machine into something it could not recover from. Hence the reload dialog.
So, I can only refer to the usual hints:
- Keep your phone connected to a charger
- Ensure good network connectivity on both devices
I can understand that this is dissatisfying but we will not mess with the state machine any more since it would be a lot of work that would defer working on the replacement of Threema Web which intends to address this and many other issues.