Microsoft authenticator for android Cloud Backup not working

VASS Dimi 1 Reputation point
2022-05-07T18:52:57.637+00:00

There must be a problem enabling cloud backup on Microsoft authenticator app on Android. Tried to enable on my account but there was an error enabling and I had to send Microsoft the log files.
Tried with a totally new Microsoft account , created, added Microsoft authenticator and when I tried to enable cloud backup the same problem appeared. 3 different android phones ( android 12, 9).
This error appeared this week. Tried using wifi or cellular, with provider DNS and Google dns . Same error .
What is happening ?

Microsoft Authenticator
Microsoft Authenticator
A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation.
6,036 questions
{count} votes

3 answers

Sort by: Most helpful
  1. rrrrrzzzzz 1 Reputation point
    2022-05-07T21:44:27.353+00:00

    this is a widespread known issue by authenticator users. unfortunately ms refused to acknowledge this.


  2. VASS Dimi 1 Reputation point
    2022-05-08T20:48:18.623+00:00

    No , this is not the case .
    I don't see any error like the one you described:
    Following part of the log file

    2022-05-08 20:42:07,779 INFO/DID_SDK/: Failed to get accessToken [DefaultDispatcher-worker-1]
    2022-05-08 20:42:07,780 INFO/DID_SDK/: com.microsoft.did.sdk.util.controlflow.AuthenticationException: Exception while getting accessToken
    at com.microsoft.authenticator.features.did.DidAccountAndAuthenticationProvider.getAccessTokenForAccount(DidAccountAndAuthenticationProvider.kt:43)
    at com.microsoft.authenticator.features.did.DidAccountAndAuthenticationProvider$getAccessTokenForAccount$1.invokeSuspend(Unknown Source:12)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at kotlinx.coroutines.UndispatchedCoroutine.afterResume(CoroutineContext.kt:142)
    at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
    at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
    at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
    Caused by: com.microsoft.tokenshare.AccountNotFoundException: MSAL failed to get account
    at com.microsoft.authenticator.authentication.aad.abstraction.MsalTokenRefreshManager$getTokenSilentlyAsync$$inlined$suspendCoroutine$lambda$1.onTaskCompleted(MsalTokenRefreshManager.kt:552)
    at com.microsoft.identity.client.MultipleAccountPublicClientApplication$3$1.onTaskCompleted(MultipleAccountPublicClientApplication.java:237)
    at com.microsoft.identity.client.MultipleAccountPublicClientApplication$3$1.onTaskCompleted(MultipleAccountPublicClientApplication.java:232)
    at com.microsoft.identity.common.java.controllers.CommandDispatcher.commandCallbackOnTaskCompleted(CommandDispatcher.java:541)
    at com.microsoft.identity.common.java.controllers.CommandDispatcher.access$1100(CommandDispatcher.java:85)
    at com.microsoft.identity.common.java.controllers.CommandDispatcher$4.run(CommandDispatcher.java:517)
    at android.os.Handler.handleCallback(Handler.java:938)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loopOnce(Looper.java:226)
    at android.os.Looper.loop(Looper.java:313)
    at android.app.ActivityThread.main(ActivityThread.java:8663)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)
    [DefaultDispatcher-worker-1]


  3. VASS Dimi 1 Reputation point
    2022-05-10T04:15:08.94+00:00

    Finally fixed. Back to normal state.