Did you enable the 2FA code using the mobile app or the desktop app?

Jase2985:

30 seconds is fine for millions of people on hundreds of different services that use this type of authentication. keeping the code after 30 seconds defeats the purpose of having the 30 second time limit in the first place and is not how this is suppose to work

you seem to be the only one having issues here, it looked like i was having the same issues then i worked out it was a time error between devices, reset the time on the 2 PC's and it was gone.

your symptoms seem almost identical.

+ you havent answered some of the above questions, how much different is the time remaining for the code in the desktop app vs the phone app?

 

freitasm:

Did you enable the 2FA code using the mobile app or the desktop app?

freitasm:

Did you enable the 2FA code using the mobile app or the desktop app?

Jase2985: you can keep going on about the 30 second time difference but hundreds of different sites use that as their time base so that's not the issue here. just learnt not to copy the code when use less than 10 seconds left and you can't make it over to paste it into the other window and time.

Does the phone app and the desktop app have the same code on a screen at the same time? I'm guessing not because you say there is a 31 second time difference

Try this:
1. Open the mobile authy app select geekzone
2. watch the code in when it resets to the next code open the authy desktop app
3. Are the codes the same?
4. if they are the same keep watching till they click over to the next code are they both on the same code? or did one reset the time but not change the code?
5. Is the countdown timer the same? All slightly different?
6. if they are different I would check the windows clock vs the phone clock and confirm that they are on exactly the same time. if not reset the windows clock to that of the phone clock to make sure they are in sync.

That is what I did and then as what fixed my issue. Wasn't just happening for geekzoneI either it was happening for all the sites I use authy for.

I have also had trouble in the past and I suspect due to the same issue. Eventually realised that the threat model for my Geekzone login doesn't justify such drastic security measures so I turned it off.

Baboon:

Jase2985: you can keep going on about the 30 second time difference but hundreds of different sites use that as their time base so that's not the issue here. just learnt not to copy the code when use less than 10 seconds left and you can't make it over to paste it into the other window and time.

Does the phone app and the desktop app have the same code on a screen at the same time? I'm guessing not because you say there is a 31 second time difference

Try this:
1. Open the mobile authy app select geekzone
2. watch the code in when it resets to the next code open the authy desktop app
3. Are the codes the same?
4. if they are the same keep watching till they click over to the next code are they both on the same code? or did one reset the time but not change the code?
5. Is the countdown timer the same? All slightly different?
6. if they are different I would check the windows clock vs the phone clock and confirm that they are on exactly the same time. if not reset the windows clock to that of the phone clock to make sure they are in sync.

That is what I did and then as what fixed my issue. Wasn't just happening for geekzoneI either it was happening for all the sites I use authy for.

I have already stated that there is no clock difference between my devices, a few times now; but there is a time differential between code display in Authy apps, with my having stated I witness desktop Authy displaying the codes later than mobile Authy, with my having further stated above that I witnessed a 31 second time differential in code display today, and 28 seconds yesterday.

I cannot be clearer than I have already been in both this post and previously. I have stated these facts in black and white multiple times now. I do not know what else I can do for you.

humor me and do the above and answer the questions. there is something missing.

im trying to help so stop getting your back up. the above worked for me and your symptoms appear identical so maybe just try it.

@Jase2985 I think you should let it go. The OP answered this already for my intents.

It certainly seems to be a bug in the desktop app.  The code is the same when a token is opened simultaneously on the android app and the desktop app but the desktop app rolls the same code over into the next 30 sec period, making it 30 secs out of sync thereafter.  Clicking the back arrow and reopening the token in the desktop app will realign the code and the countdown with the android app but because the desktop token is newly reopened it will again fail to update the code after the first timeout. 

Baboon: Unfortunately, our desktop version does have a bug that's has been recently spotted, which prevents the tokens from updating on the first 30 seconds.

I'm sincerely sorry, but I am not able to give you an approximate date for this fix to be deployed since our product schedule is pretty tight at the moment. However, I can assure you that our team is always working on improving our performance and user's experience and that this will be taken care of as soon as possible.

 

Crappy answer. It's a serious bug. It keeps people out of their services. In between putting a new feature or fixing this bug, I'd go with the fix.

Baboon:

I'm sincerely sorry, but I am not able to give you an approximate date for this fix to be deployed since our product schedule is pretty tight at the moment.

That's completely inexcusable to me. If there is a app breaking bug it should supersede any product schedule.