You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VS2022 prompting to login to access CommunityToolkit-Labs and CommunityToolkit-MainLatest feeds #664
While updating nugets I got prompted to sign-in to see the public labs/latest nuget feeds. The dialog presented me with multiple accounts I am currently logged in with. Selecting the one I use for VS2022 did nothing as the prompt appears again about 5 minutes later.
The login window only appears when I go to update nugets, which means I am unsure if it is related to Visual Studio update or not as I don't recall the last time I was in looking at nuget updates.
Steps to reproduce
Add private nuget feeds
CommunityToolkit - Toolkit Labs
https://pkgs.dev.azure.com/dotnet/CommunityToolkit/_packaging/CommunityToolkit-Labs/nuget/v3/index.json
CommunityToolkit - MainLatest
https://pkgs.dev.azure.com/dotnet/CommunityToolkit/_packaging/CommunityToolkit-MainLatest/nuget/v3/index.json
Try search for packages and get prompted with a login window.
Expected behavior
I am not required to login.
Screenshots
Code Platform
UWP
WinAppSDK / WinUI 3
Web Assembly (WASM)
Android
iOS
MacOS
Linux / GTK
Windows Build Number
Windows 10 1809 (Build 17763)
Windows 10 1903 (Build 18362)
Windows 10 1909 (Build 18363)
Windows 10 2004 (Build 19041)
Windows 10 20H2 (Build 19042)
Windows 10 21H1 (Build 19043)
Windows 10 21H2 (Build 19044)
Windows 10 22H2 (Build 19045)
Windows 11 21H2 (Build 22000)
Other (specify)
Other Windows Build number
Windows 11 24H2 26100.3624
App minimum and target SDK version
Windows 10, version 1809 (Build 17763)
Windows 10, version 1903 (Build 18362)
Windows 10, version 1909 (Build 18363)
Windows 10, version 2004 (Build 19041)
Windows 10, version 2104 (Build 20348)
Windows 11, version 22H2 (Build 22000)
Other (specify)
Other SDK version
No response
Visual Studio Version
2022
Visual Studio Build Number
17.13.5
Device form factor
Desktop
Additional context
No response
Help us help you
No, I'm unable to contribute a solution.
Reacted by Jan Philipp Weber, Shimmy Weitzhandler and Tim Vilgot Mikael Fredenberg
I was experiencing the same issue, and reported it in the Labs repo: CommunityToolkit/Labs-Windows#662.
I also found a workaround, which I'm curious if would work for you as well.
@Arlodotexe should we have a tracking issue elsewhere for Labs? This is beyond Toolkit, as we haven't changed anything (at least actively) here. I've just posted in the .NET Foundation discord to see if others are hitting this as well.
There was an update over here, this should now be resolved.
The VulnerabilityInfo/6.70 resource component in the NuGet server's index.json was inadvertently made available due to a misconfiguration. It has now been removed from the index.json, and the authentication error should be mitigated.
Activity
weitzhandler commentedon Mar 29, 2025
Hi,
I was experiencing the same issue, and reported it in the Labs repo: CommunityToolkit/Labs-Windows#662.
I also found a workaround, which I'm curious if would work for you as well.
beeradmoore commentedon Mar 29, 2025
I was previously doing the same as @weitzhandler solution.
But the issue also appears to not be happening anymore. Maybe a temp issue with azure feed?EDIT: Nevermind, it came back.
beeradmoore commentedon Mar 31, 2025
@Arlodotexe , I don't think this issue is not related to that PR.
This issue is using that feed in our own apps is prompting for authentication.
michael-hawker commentedon Apr 2, 2025
@Arlodotexe should we have a tracking issue elsewhere for Labs? This is beyond Toolkit, as we haven't changed anything (at least actively) here. I've just posted in the .NET Foundation discord to see if others are hitting this as well.
lostmsu commentedon Apr 10, 2025
@Arlodotexe this is still happening with https://pkgs.dev.azure.com/dotnet/CommunityToolkit/_packaging/CommunityToolkit-Labs/nuget/v3/index.json
beeradmoore commentedon Apr 16, 2025
There was an update over here, this should now be resolved.