Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Can not push symbols nuget package #2837
Before we use nuget version 2.8.6, and we can use command,
We can successfully push package to nuget.org and source code to http://www.SymbolSource.org.
Today, when I try the command again, I will get issue to push symbols,
Then I download newest stable nuget, 22.214.171.1245,
nuget.exe push package.symbols.nupkg -Source https://nuget.smbsrc.net -ApiKey 8a07038c-1e59-4a3f-9615-01f3a13b651a
nuget.exe push package.symbols.nupkg -Source https://nuget.smbsrc.net
None of them works, it still requests me to input a ApiKey, and nuget ApiKey does not work.
Then question is,
Yes, the old symbol server is now deprecated, you should use the new server which is https://nuget.smbsrc.net/. Can you try the following and let us know if it doesnt work.
nuget.exe setApiKey 8a07038c-1e59-4a3f-9615-01f3a13b651a
nuget.exe push %packagename% -Source https://nuget.smbsrc.net/. You are missing the trailing forward slash that might cause issues (it does for sure when you specify the symbol server in VS)
Symbol packges should get pushed automatically provided there are available, to the new endpoint when you push a package
For binary push, you need to specify the source going forward. This is a recent breaking change.
I figure out this one works for me with nugget 3.4.3,
nuget.exe push Microsoft.Restier.0.5.0-beta.symbols.nupkg 8a07038c-1e59-4a3f-9615-xxxxxxxxx -Source https://nuget.smbsrc.net
set the apikey first and the run push does not work for me.
I close the issue as I have a way to work, but I prefer we can update nugget help message if this is the only work command.
This should work, we will take a look at this. Our docs says we suppor this https://docs.nuget.org/create/creating-and-publishing-a-symbol-package
@rrelyea The client used to have some logic that would change the push URL. I believe it checks for the gallery push URL and a .symbols.nupkg file. If that is the case, SymSrc is used as the source instead. When pushing, SymSrc.org calls into the gallery to validate the API key used.