Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
NuGet package has no symbols - No symbols in this package have been indexed.
-
Command to build the NuGet package:
"C:\Program Files\dotnet\dotnet.exe" pack Q:\MyPackage\src\MyPackage.csproj --configuration Release --no-build --no-restore --no-dependencies --property:SymbolPackageFormat=snupkg --output Q:\MyPackage\result\nuget
Output:
15:52:05 [DBG] Successfully created package 'Q:\MyPackage\result\nuget\MyPackage.9.2.4.183.nupkg'. 15:52:05 [DBG] Successfully created package 'Q:\MyPackage\result\nuget\MyPackage.9.2.4.183.snupkg'.
Command to push the package to ProGet
15:52:05 [INF] > "C:\Program Files\dotnet\dotnet.exe" nuget push Q:\MyPackage\result\nuget\MyPackage.9.2.4.183.nupkg --source https://proget:8624/nuget/MyFeed/
Output:
15:52:05 [DBG] warn : No API Key was provided and no API Key could be found for 'https://proget:8624/nuget/MyFeed/'. To save an API Key for a source use the 'setApiKey' command. 15:52:05 [DBG] Pushing MyPackage.9.2.4.183.nupkg to 'https://proget:8624/nuget/MyFeed/'... 15:52:05 [DBG] PUT https://proget:8624/nuget/MyFeed/ 15:52:06 [DBG] Created https://proget:8624/nuget/MyFeed/ 189ms 15:52:06 [DBG] Your package was pushed.
Command to push the symbols of the package (snupkg )
15:52:06 [INF] > "C:\Program Files\dotnet\dotnet.exe" nuget push Q:\MyPackage\result\nuget\MyPackage.9.2.4.183.snupkg --source https://proget:8624/nuget/MyFeed/
ProGet shows
No symbols in this package have been indexed.
in the details of the package version under Symbols.
The symbol server for the feed is configured and set toStandard (.snupkg format)
I tried to change the order of the push commands => no change, still no symbols.
I tried to re-index the feed => no change, still no symbols.ProGet shows no errors in the
Diagnostic Center
.What can I do to troubleshoot this issue?
-
Hi @ds_6782 ,
If you haven't already ,I would make sure to check out the docs here:
https://docs.inedo.com/docs/proget/feeds/nuget/symbol-and-source-serverThe NuGet client will automatically push both packages when you issue the
dotnet nuget push
command. You do not need to push then separately.It looks like, for whatever reason ,your NuGet client isn't doing that? We don't see this problem very often - it "just works" - and I'm not really an expert at troubleshooting NuGet client configuration.
But that's where I would start. It looks like the issue is on the client end, and somehow your clientis misconfigured to not push the source packages.
Thanks,
Steve
-
Hi Steve
Thanks for your response.
I've read the documentation and for the client part I followed the Microsoft documentation:
https://learn.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkgAfter some testing, I've found the problem:
I had to add/v3/index.json
to the URL. Now the package and the symbols are pushed to the server.
The ProGet UI shows the correct URL underAPI endpoint URL:
. I'm not sure why my build script was using the URL withoutv3
. Maybe it was different in an older version of ProGet or I just made a mistake somewhere?Interesting is that pushing "worked" when using the URL without
v3
and v2 API disabled for the feed.
Maybe the client NuGet client contains some logic to only push the snupkg file when it detects a v3 source?