none
Microsoft Authenticator App is Producing Invalid Codes RRS feed

  • Question

  • Since the most recent update to the Microsoft Authenticator app, it is unable to produce valid codes for any of my online 2FA services.

    This is on an Android device.

    Looking at the reviews in the Play Store, this seems to be an issue affecting a number of users.

    Please could you provide us with an acknowledgement that this is a known issue and a rough idea of when a fix may be released, at the moment I am having to use backup methods to access a lot of my online accounts.

    I have confirmed that the clock settings on my device are correct.

    Thank you

    Monday, September 25, 2017 7:41 PM

All replies

  • It happens to me too :(

    Monday, September 25, 2017 11:51 PM
  • Hi

    What is the version of your Phone and Microsoft Authenticator APP?

    If possible, you could try delete the accounts on Microsoft Authenticator App and re-add them.

    Regards,

    Walter


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, September 26, 2017 6:44 AM
  • For me, Android 7.0 (Samsung S8+) and app version 6.2.4

    Tuesday, September 26, 2017 1:36 PM
  • Same here, and others. I see your PM mentioned on Twitter that a hotfix is due, but still pending. I have tried both versions 6.2.4 and 6.2.5, but the codes are still invalid. I have tried going back to old APKs, but they won't install. Deleting an account is not always an option, in some cases I'll lose access to the account. 
    Tuesday, September 26, 2017 5:00 PM
  • We introduced a regression in Android build 5.2.4, that would impact some users' OTP codes in app upgrade scenarios. 

    We have a fix in beta, it is expected to return a user in this state to a full working condition without needing to remove and re-add the account. You can self-select into the beta by going into the Help menu and selecting "Get an early preview." We will be rolling out the app to all users over the course of the next couple of days. 


    Sincere apologies for the issue, we realize this was a serious productivity hit for those who rely on OTP codes. 
    Tuesday, September 26, 2017 11:10 PM
  • Hi, are you in the Beta program, and the update didn't fix your issue? would you mind sending your logs (Help > Send Logs) and reply back here with the Incident ID? 

    Thanks! 

    Tuesday, September 26, 2017 11:12 PM
  • Hi, are you in the Beta program, and the update didn't fix your issue? would you mind sending your logs (Help > Send Logs) and reply back here with the Incident ID? 

    Thanks! 


    Thanks. Yes, I'm in the Beta program and using 6.2.5. I wasn't aware this was the hotfix version. Anyway, it didn't fix my issue, still showing incorrect codes. The Incident ID is K57SVZGY.
    Wednesday, September 27, 2017 4:40 AM
  • This is an incredible error. It has locked me out of all my banking and trading apps for 2 days and has cost me thousands of dollars. Where would be the appropriate place to complain about this?

    Wednesday, September 27, 2017 11:42 AM
  • Hi,

    Not to be impatient...but...it's hard not to be!  This glitch is now causing some serious stress and may soon start costing money.  Even if I contact all the companies I have accounts with to disable and re-enable the 2fa on those accounts, it's going to take several business days to complete.

    Please tell me the fix is almost in place...??  And that it will alleviate all current issues...??

    Thanks.

    Thursday, September 28, 2017 11:53 PM
  • Hi,

    Not to be impatient...but...it's hard not to be!  This glitch is now causing some serious stress and may soon start costing money.  Even if I contact all the companies I have accounts with to disable and re-enable the 2fa on those accounts, it's going to take several business days to complete.

    Please tell me the fix is almost in place...??  And that it will alleviate all current issues...??

    Thanks.

    Thursday, September 28, 2017 11:54 PM
  • Version 6.2.6 finally fixes the problem. You can get it by joining the Beta program.
    Friday, September 29, 2017 4:14 AM
  • Great!  Will try immediately!  Previous comments said the Beta version wasn't working or I would've tried already.

    Thanks!

    Friday, September 29, 2017 2:52 PM
  • The same exact thing is happening to me too. I cannot for some reason get valid codes so I hope they fix this.
    Saturday, November 24, 2018 8:33 PM