Skip to content

[MSAL] Settings Sync logs out very quickly (few mins to few hours) - Error Code 2156265475 #244939

Closed
Closed
[MSAL] Settings Sync logs out very quickly (few mins to few hours) - Error Code 2156265475#244939
Assignees
TylerLeonhardt
Labels
authentication-microsoftIssues with the Microsoft Authentication extensionbugIssue identified by VS Code Team member as probable bugupstreamIssue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeeded
Milestone
April 2025

Description

@manastalukdar
Manas Talukdar (manastalukdar)
opened on Mar 28, 2025

Update by maintainer

You can help us tremendously by following the steps below to get logs.

Two workarounds

  1. VS Code Insiders which has the fix
  2. Alternatively, to unblock yourself temporarily apply this setting, but remember to disable it in May: 
    "microsoft-authentication.implementation": "classic"
    You can do so by open the settings with Preferences: Open Settings command in the Command Palette

Original issue

Version: 1.99.0-insider (system setup)
Commit: ff52a0d
Date: 2025-03-27T05:04:01.081Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Steps to Reproduce:

  1. Log into settings sync.
  2. get prompted to log in few mins (to few hours) later. Have to log in multiple times a day.

This was reported previously under #229456.

Activity

  1. Imagevs-code-engineering
    assigned
    Sandeep Somavarapu (sandy081)
    on Mar 28, 2025

  2. manastalukdar commented on Mar 28, 2025

    @manastalukdar
    Manas Talukdar (manastalukdar)
    on Mar 28, 2025
    Author

    I have temporarily the AuthN mode to classic, but that will soon be deprecated, so it is obviously not a solution.

  3. ImageSandeep Somavarapu (sandy081)
    assigned
    TylerLeonhardt
    and unassigned
    Sandeep Somavarapu (sandy081)
    on Mar 28, 2025

  4. TylerLeonhardt commented on Mar 28, 2025

    @TylerLeonhardt
    TylerLeonhardt
    on Mar 28, 2025
    Member

    Can you follow these steps so that we can get more information on what's going on?

    Enable trace logging

    • Open the Command Palette (cmd/ctrl+shift+p)
    • Run the Developer: Set Log Level... command
    • To the right of Trace, click the double check mark button. ✔️ ✔️ (enables trace logging as the default)

    Now wait for the issue to happen or trigger it...

    Getting the logs

    • Open the Command Palette again (cmd/ctrl+shift+p)
    • Run the Output: Show Output Channels... command
    • Choose Microsoft Authentication
    • Copy and paste the contents of what opens in the panel in this issue (if the contents is too large, you may need to upload it as a file)

    Reverting trace logging (optional)

    When we're done here, to revert the log level back to the default:

    • Open the Command Palette
    • Run the Developer: Set Log Level... command
    • To the right of Info, click the double check mark button. ✔️ ✔️ (to set the default back to info)
  5. ImageTylerLeonhardt
    added
    info-neededIssue requires more information from poster
    on Mar 28, 2025

  6. manastalukdar commented on Mar 29, 2025

    @manastalukdar
    Manas Talukdar (manastalukdar)
    on Mar 29, 2025
    Author

    msal.log

  7. TylerLeonhardt commented on Mar 31, 2025

    @TylerLeonhardt
    TylerLeonhardt
    on Mar 31, 2025
    Member

    Error's I've noticed:

    2025-03-28 20:34:42.691 [error] [Sat, 29 Mar 2025 03:34:42 GMT] : [04f0c124-f2bc-4f59-8241-bf6df9866bbd] : @azure/msal-node-extensions@1.5.0 : Error - [MSAL:0002] ERROR Create:27 Created an error: tag_7cisv, StatusInternal::Unexpected, SubStatusInternal::0

    2025-03-29 00:43:24.849 [error] [Sat, 29 Mar 2025 07:43:24 GMT] : [04f0c124-f2bc-4f59-8241-bf6df9866bbd] : @azure/msal-node-extensions@1.5.0 : Error - [MSAL:0003] ERROR ErrorInternalImpl:134 Created an error: 7q6cc, StatusInternal::ApiContractViolation, InternalEvent::None, Error Code 2156265475, Context '(pii)'

    It looks like this issue is related to the Microsoft Identity authentication broker on your OS. This is not a component maintained by VS Code - It simply leverages it for authentication.

    Please refer to the Feedback and support section of this post for assistance with these types of issues. This article also talks about what authentication brokers are and why they're important.

    Closing this as out of scope of VS Code...

  8. ImageTylerLeonhardt
    closed this as not plannedon Mar 31, 2025
  9. ImageTylerLeonhardt
    reopened this on Apr 8, 2025
  10. ImageTylerLeonhardt
    added
    bugIssue identified by VS Code Team member as probable bug
    upstreamIssue identified as 'upstream' component related (exists outside of VS Code)
    authentication-microsoftIssues with the Microsoft Authentication extension
    and removed
    info-neededIssue requires more information from poster
    on Apr 8, 2025
  11. ImageTylerLeonhardt
    added this to the Backlog milestone on Apr 8, 2025

  12. 25 remaining items

  13. TylerLeonhardt commented on Apr 22, 2025

    @TylerLeonhardt
    TylerLeonhardt
    on Apr 22, 2025
    Member

    Identity team has a proposed fix and will ideally have something for us this week to consume. Thank you all for your help tracking down the issue.

  14. TylerLeonhardt commented on Apr 25, 2025

    @TylerLeonhardt
    TylerLeonhardt
    on Apr 25, 2025
    Member

    The new build of the MSAL runtime has been released in Insiders so this issue should be fixed.

    Please acquire VS Code Insiders which has the fix and let me know if you still see the issue.

    It will be in the next VS Code stable targeted for early May.

  15. ImageTylerLeonhardt
    closed this as completedon Apr 25, 2025
  16. ImageTylerLeonhardt
    modified the milestones: Backlog, April 2025 on Apr 25, 2025

  17. TylerLeonhardt commented on Apr 25, 2025

    @TylerLeonhardt
    TylerLeonhardt
    on Apr 25, 2025
    Member

    Verification:

    • Sign in to Settings Sync or some other feature that uses Microsoft login but using a Personal Microsoft account
    • Wait at least 2hrs and see if you're still signed in

  18. zse4t7i commented on Apr 26, 2025

    @zse4t7i
    zse4t7i (zse4t7i)
    on Apr 26, 2025

    It works well.

  19. ImageConnor Peet (connor4312)
    added
    verifiedVerification succeeded
    on Apr 30, 2025

  20. NicolasVitorP commented on May 5, 2025

    @NicolasVitorP
    Nick (NicolasVitorP)
    on May 5, 2025

    Have you fixed the bug in the stable version?

  21. sascharo commented on May 5, 2025

    @sascharo
    Sascha Roman Robitzki (sascharo)
    on May 5, 2025

    Have you fixed the bug in the stable version?

    It appears like that to me. At least the current stable version: 1.99.3 stays logged in for me. Or is that just a coincidence?

  22. racile commented on May 6, 2025

    @racile
    Raven Tabanao Kavoori (racile)
    on May 6, 2025

    The issue persists. I have two accounts logged in GitHub for Copilot and Microsoft authentication for sync settings. GitHub works fine, but after signing in with Microsoft for sync settings, VSCode prompts me to sign in again upon reopening.

    Version: 1.99.3 (system setup)
Commit: 17baf841131aa23349f217ca7c570c76ee87b957
Date: 2025-04-15T23:18:46.076Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

  23. zse4t7i commented on May 7, 2025

    @zse4t7i
    zse4t7i (zse4t7i)
    on May 7, 2025

    It will be in the next VS Code stable targeted for early May.

    Maybe you can try the update which was released today or tomorrow.

  24. racile commented on May 9, 2025

    @racile
    Raven Tabanao Kavoori (racile)
    on May 9, 2025

    fixed, thank you

    Version: 1.100.0 (system setup)
Commit: 19e0f9e681ecb8e5c09d8784acaa601316ca4571
Date: 2025-05-07T12:48:53.763Z
Electron: 34.5.1
ElectronBuildId: 11369351
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

  25. zrivkis commented on May 9, 2025

    @zrivkis
    Ziv Rivkis (zrivkis)
    on May 9, 2025

    Can confirm that ver 1.100.0 is behaving correctly using the MSAL implementation. Haven't been signed out in over an hour.
    TylerLeonhardt - thank you for your hard work and support in getting this issue resolved!

    Version: 1.100.0 (user setup)
Commit: 19e0f9e681ecb8e5c09d8784acaa601316ca4571
Date: 2025-05-07T12:48:53.763Z
Electron: 34.5.1
ElectronBuildId: 11369351
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
  26. Imagevs-code-engineering
    locked and limited conversation to collaborators on Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

authentication-microsoftIssues with the Microsoft Authentication extensionbugIssue identified by VS Code Team member as probable bugupstreamIssue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeeded

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions