Last token keeps being displayed indefinitely

[ahamro]

Bug type

Other

App version

5.3.6

Device environment

iOS 17.5 (beta)
Watch SE 2022
iPhone 12

Bug description

After producing a token and then leaving the watch as it is (so not going back to the tokens list)
and then after say 20 minutes open 2FAS again, it sometimes still shows the last token, which is no longer valid of course.
Where normally the remaining time for the current token is displayed, there is now the time lapsed since the token was produced.
To get a fresh token I have to use the red arrow left (upper left), go to the list and select the token again.

Solution

No response

Additional context

No response

Acknowledgements

• This issue is not a duplicate of an existing bug report.
• I understand that security vulnerabilities should be reported to [email protected] instead of on GitHub.
• I have chosen an appropriate title.
• All requested information has been provided properly.

[fe-fred]

I have the same problem on iOS 17.5.1 and watchOS 10.5.

[hondaspb]

I have the same problem on iOS 17.5.1 iPhone 12 widget shows codes which are no longer valid and the countdown timer shows time since the last code was issued which is obviously not valid. Same bug as #71

[ahamro]

In version 5.3.7 the bug is still there.

I tried Bitwarden's companion app and it does not show this behaviour. And also very convenient: it has a watch complication.
But still I'd prefer to start using 2FAS.

[warwickmm]

I'm still experiencing this as well, coincidentally also with an iPhone 12 (mini).

[adocyn]

Hi, this issue comes from the fact, that we're supporting the refresh on always-on screen. The watch asks the app for the "time points" when code will change and code values. We're feeding that info to the system. Then it takes over and at given time point it refreshes the code with provided values. The problem is that generating those time points takes time (every token value has to be calculated for future change in time) and you can spend on that only limited amount of time and feed the system a limited amount of data. How much? No spec for that. Differs per device. It's fun ....

The same mechanism is used on widget. It worked great for iOS 16, but on iOS 17 system doesn't ask for new "time points" when it runs out of the current ones. That's why the screen doesn't refresh sometimes. Same issue on watch. It takes 2 - 3 minutes before there's a call to app to provide new data. Why Apple did change that - don't know. But it makes working with such data so much worse. Anyway we're looking for solutions to that.