microsoft / microsoft/aspire-samples
[WebToolsE2E][Aspire] Registration or login failed after successfully deploying the Aspire-Samples/VolumeMount solution.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 345
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 30
Description
REGRESSION INFO: Also repro on Aspire 8.0.0-preview.3.24105.21
INSTALL STEPS
- Clean machine: Win11 x64 23h2 ENU
- Install VS 17.10 Preview 2 [ includes Aspire 8.0.0-preview.4.24128.4 ]
- Apply NuGet dotnet-tools Feeds
- Install Docker Desktop for Windows
- Install latest azd
REPRO STEPS
- Clone aspire-samples repo from main branch
- Checkout the
Preview.4branch - Update sdk version to
8.0.300-preview.24101.10in global.json - Update Aspire version to latest
8.0.0-preview.4.24128.4in Directory.Packages.props - Open samples\VolumeMount.sln
- Set the sqlpassword and postgrespassword key in the User Secrets store of the VolumeMount.AppHost project using the dotnet user-secrets command in the AppHost project directory:
dotnet user-secrets set sqlpassword <password>
dotnet user-secrets set postgrespassword <password> - Build
- Deploy using azd
- Open the solution folder in a Command Prompt
- Runing 'azd init', select 'Use code in the current directory' > Confirm and continue initializing my app, type a new environment name, press enter.
- When running azd init choose to expose 'blazorweb' to the Internet
- Run azd up to deploy to Azure
- Click on the deployed blazorweb endpoint and then register or login to a account.
ACTUAL:
Error.
An error occurred while processing your request.
Request ID: 00-fef7d4410c56ee315b10c4c10d6bc08f-b5fa6c1627e90fb2-01
Development Mode
Swapping to Development environment will display more detailed information about the error that occurred.
The Development environment shouldn't be enabled for deployed applications. It can result in displaying sensitive information from exceptions to end users. For local debugging, enable the Development environment by setting the ASPNETCORE_ENVIRONMENT environment variable to Development and restarting the app.
Note
- This issue is also reproduced using VS deployment.
Additional Info
EXPECTED
After successful deployment,there are no errors in registering or logining to a account.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with samples\VolumeMount.sln and the VolumeMount.AppHost project, following the listed user-secrets setup and azd deployment steps. Reproduce the failure at the deployed blazorweb endpoint, then inspect the deployment error associated with the provided request ID and compare it with the VS deployment result. Done means registration and login work after deployment without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, docker
- Domain
- authentication, cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100