Activities of "ddelamare"

Uploaded new repro

I followed these steps on my real project instead of the stripped down one and it didn't work. The proxies generated, and I switched to the static proxies in the http client project and then my blazor project wouldn't even launch. It was giving me initialization errors: 'TOG.WorkOrders.WorkOrderAttachmentTypeClientProxy.GetAttachmentTypeByIdAsync (TOG.HttpApi.Client)' has ApiExplorer enabled, but is using conventional routing. Only actions which use attribute routing support ApiExplorer.. See the inner exception for details.

Not sure if it's relevant, but that endpoint is inherited from a base attachment app service, so perhaps the routing model is different.

Is there a way to make this work with dynamic proxy generation? Is Blazor WebApp not compatible with the tiered model?

I have sent via wetransfer

I have emailed you a reproducible project. After running the migrator, you should be able to log in with the admin password System123!

After the site loads and login, the site will appear functional for some time, then with no user interaction go to an error screen and the console will be full of errors.

After completing all these steps, particularly changing the base url of the client project, I now get this error:

:44346 is the port of the Blazor WebApp.

Sent via email.

I have tried all these steps above, except the custom authentication state. Notably, the boilerplate bootstrapped project provided by ABP also does not work.

• Steps to reproduce the issue:
• We are migrating our current Blazer WebAssembly app into the new Blazor WebApp format and we are seeing an issue where after a user logs in, a few seconds later with no user interaction, it will switch from SSR/Server rendered to WASM rendered, but the user will be logged out. Notably this does not happen when the HeadOutlet rendermode is set to InteractiveServer, but only when everything is InteractiveAuto. I encountered this same issue in the sample project bootstrap. There is no output in the logs besides

See the sample photos below

I am seeing wrong icons in the popups and now I am seeing them in the data grids.

• ABP Framework version: v8.1.4
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Exception message and full stack trace: N/A
• Steps to reproduce the issue: Show an error dialog.

After upgrading to 8.1.4, strange icons are being shown in the alert windows. I am using Blazorise 1.5.3 with the FontAwesome Icons package installed. Instead of the usual "X" icon when an exception occurs it is showing a StepForward icon. I did some digging and this seems to come from the Volo.Abp.BlazoriseUI 8.1.4 dll which I decompiled to find this

which is different than the GitHub source which lists the the Error icon should be a Times.