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-snupkg

After 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 under API endpoint URL:. I'm not sure why my build script was using the URL without v3. 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?

Hi Steve

Thanks for your answer.

I saw this in the doc and thought it will use v3 https://learn.microsoft.com/en-us/nuget/api/search-query-service-resource

It is possible to search for packages available on a package source using the V3 API. The resource used for searching is the SearchQueryService resource found in the service index.

In this case, sorry for the question and please forget it^^

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 to Standard (.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?

Running this nuget command:

nuget search MyPackage -PreRelease -Source https://proget:8624/nuget/MyFeed/

results in this error when v2 api is not enabled for the feed

The V2 feed at 'https://proget:8624/nuget/MyFeed/Search()?$filter=IsAbsoluteLatestVersion&searchTerm='MyPackage'&targetFramework=''&includePrerelease=true&$skip=0&$top=20&semVerLevel=2.0.0' returned an unexpected status code '400 Bad Request'.