threema-web icon indicating copy to clipboard operation
threema-web copied to clipboard

Threema app shows I am connected with session although I am not

Open ovalseven8 opened this issue 6 years ago • 9 comments

Just found this. Don't know if there is a way to make it reproducible.

screenshot_20170907-221548

Your Environment

  • Threema Web version: 1.5.0
  • Threema for Android version: 3.19.2000369

ovalseven8 avatar Sep 07 '17 20:09 ovalseven8

Found a way to make it reproducible:

  1. Go the the "Threema Web" menu in the app
  2. Reconnect to session

Now, if I immediately stop the session everything is ok. However:

  1. Wait some time until your smartphone turns off light/is locked
  2. Stop session (in browser!)

Now, if you unlock your phone you'll see that the icon in the "Threema Web" menu is still green although one is not connected anymore. If I go to another page and then go back to the "Threema Web" menu everything is okay again. But anyway, that's a bug. ;)

Could you reproduce?

ovalseven8 avatar Sep 07 '17 20:09 ovalseven8

I think I experienced this issue, too. When you then try to start the connection again the icon in the app always turns red and goes crazy more or less. In any case then I always had to force-close Threema, and sometimes even create a new connection (i.e. scan a new QR code) and delete the old one, which was still showing the red warning icon.

rugk avatar Sep 07 '17 23:09 rugk

There were a few state transitions that weren't covered in the current release, resulting in strange behavior and/or crashes. This is probably fixed in the current development version and will be released in the next beta.

dbrgn avatar Sep 08 '17 07:09 dbrgn

This is probably fixed in the current development version and will be released in the next beta.

Just installed the new beta (3.19.2000370), but issue is NOT fixed.

ovalseven8 avatar Sep 09 '17 09:09 ovalseven8

Sorry, I referred to the comment by @rugk. It's possible that the state displayed at the right of a session is not always accurate yet. (We refactored the entire session handling code, so there's a lot to test and debug, and the efforts were mostly focussed on voice calls until this week. So give us some time :wink:)

dbrgn avatar Sep 09 '17 09:09 dbrgn

Yeah, yeah, no problem. Just wanted to inform you. :wink:

I guess also in previous versions of Threema this problem occurred. So it's probably not related to your refactorings.

ovalseven8 avatar Sep 09 '17 09:09 ovalseven8

Issue is still reproducible with Threema 4.0-beta2.

ovalseven8 avatar Jul 10 '19 07:07 ovalseven8

Issue is still reproducible with Threema 4.2.

ovalseven8 avatar Oct 28 '19 18:10 ovalseven8

Should be resolved with one of the next versions of Threema (depending on how long we need to test the changes), thanks to a refactoring.

dbrgn avatar Oct 29 '19 07:10 dbrgn