No secrets configured for this application. is what dotnet user-secrets list prints when the store of the project it is looking at is empty. It is not an error: the exit code was 0. If you expected values, check which project the command is looking at: in this test it was a different one from the project that held them. Run the command in that project's folder, or name it with --project.

In the test the secret lived in project Sec1; list run in the folder of a second project, Jwt1, printed this line, and list --project ..\Sec1\Sec1.csproj from the same folder printed the value.

The error

dotnet user-secrets init
Set UserSecretsId to '09527d44-3c00-46e0-b2a5-a6ca976372d1' for MSBuild project 'C:\...\cfg\Jwt1\Jwt1.csproj'.
exit=0
dotnet user-secrets list
No secrets configured for this application.
exit=0

The path is shortened; nothing else changed.

Why it happens

Each project has its own store, named by the UserSecretsId in its .csproj. Jwt1 had just been given a new id by init and nothing had been set under it, so its store was empty. The value set earlier belonged to Sec1, whose id is 514b50b0-46e6-4ccb-b589-6a3cf2aeed2e. The tool answered for the project in the current folder, and that was the wrong one. The two project folders sat side by side, and the command gave no hint that the other project held values.

Run from a folder that holds no project at all, the tool says so instead:

dotnet user-secrets list
Could not find a MSBuild project file in 'C:\...\fixes11\cfg'. Specify which project to use with the --project option. Use --file option for file-based apps.
exit=1

The fix

dotnet user-secrets list --project ..\Sec1\Sec1.csproj
Jwt:Key = fix11-test-key-not-a-real-secret-0123456789
exit=0

--project takes the project file or its folder: from the parent folder, dotnet user-secrets list --project Sec1 printed the same line. The value is a made-up string for the test. If the right project really has an empty store, set the values with dotnet user-secrets set in that project's folder, as in the Sec1 project here.

How it was reproduced

Two projects from dotnet new web -f net10.0 with SDK 11.0.100 on Windows 11. Sec1 had init and one set earlier; Jwt1 got init only. list ran in Jwt1, in the parent folder, and with --project from both. Every command shown without a PS> marker ran in cmd: a PowerShell script passed it as cmd /c ... 2>&1 and printed the exit= line after it.

Frequently asked

Why does dotnet user-secrets list say No secrets configured for this application?
The store of the project in the current folder is empty. In this test the secret had been set in another project folder; list with --project pointing at that project printed it.
How do I list user secrets for a specific project?
Pass the project file or folder: dotnet user-secrets list --project path\to\App.csproj. In this test both the folder name and the .csproj path worked.
Is No secrets configured an error?
No. The command exited with code 0. It only reports that the store for that project's UserSecretsId holds no values.

More decoded errors in the Fixes category. If list instead complains about a missing UserSecretsId, see Could not find the global property 'UserSecretsId'.