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
Describe the bug
Delay or lag in getting the newest code from phone after short idle time with Galaxy watch / Wear OS
To Reproduce
Steps to reproduce the behavior:
Log on the webapp
open Authenticator on watch
try to use code
Expected behavior
Should log on using the displayed token.
App Version
1.24.1 Phone
2.15.1 Wear OS
Additional context
The displayed code with be behind by two, or sometimes three, tokens. It will eventually cycle through to the current one, but the app or screen will have shut off by then.
The text was updated successfully, but these errors were encountered:
The codes on the watch are generated using the system clock. Do you have a time difference between your phone and the watch? That's the likeliest explanation.
Nope, same time. My guess would be some cache or syncing timing.
Some times when you open it, you'll see a code that will change after a few seconds, and sometimes the next code will only show 5-10 seconds, and then then third code is back on track.
Describe the bug
Delay or lag in getting the newest code from phone after short idle time with Galaxy watch / Wear OS
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should log on using the displayed token.
App Version
1.24.1 Phone
2.15.1 Wear OS
Additional context
The displayed code with be behind by two, or sometimes three, tokens. It will eventually cycle through to the current one, but the app or screen will have shut off by then.
The text was updated successfully, but these errors were encountered: