You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Bluetooth is disabled, the app shows the handshake status as paused in the app (yellow switch). However, if location services are disabled, the handshake status still shows the "active" status (blue switch). I know, there is a notification, but the notification can be dismissed and then the user would still assume that the exposure logging is active. To avoid confusion, it would be best if the status would be correctly reflected within the app as well.
Reproduction steps
Enable handshake with bluetooth and location services enabled.
Disable location services.
App still shows the blue active handshake switch.
Additional helpful information:
App: 2.0.0.1049-QA_240
Mobile: Oneplus 5, Android 10
What did you expect
I would expect a yellow switch for a paused handshake when location services are disabled (same as with disabled bluetooth).
The text was updated successfully, but these errors were encountered:
bauxi
changed the title
Interrupted handshake (yellow switch) not shown in app when location services are disabled
Handshake status incorrectly reflected in app when location services are turned off
Jul 16, 2020
Description
When Bluetooth is disabled, the app shows the handshake status as paused in the app (yellow switch). However, if location services are disabled, the handshake status still shows the "active" status (blue switch). I know, there is a notification, but the notification can be dismissed and then the user would still assume that the exposure logging is active. To avoid confusion, it would be best if the status would be correctly reflected within the app as well.
Reproduction steps
Additional helpful information:
What did you expect
I would expect a yellow switch for a paused handshake when location services are disabled (same as with disabled bluetooth).
The text was updated successfully, but these errors were encountered: