- ABP Framework version: v5.1.2
- UI type: Blazor Server
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace: None
- Steps to reproduce the issue:
We migrated our application from 4.3.3 to 5.0.1. This was quite difficult, as the startup template comparison alone shows so many differences.
5.0.1: Everything worked, except refreshing a sub-path (e.g. root/subpage). This would lead to duplicate path found error.
5.1.1: After updating to 5.1.1 for this fix (blazor/hotreload), clicking on "login" threw an error. But 1.5.2 was already out, so we migrated to 5.1.2
5.1.2: Here the application would start without issues. Clicking "login" properly navigates to the login site. But after a successful login, the user is still not logged in (login window closes successfully. This is different to a "wrong" login, where the error message correctly gets shown)! In backend it works, this can be checked with Swagger, where we can login & query authorized endpoints.
Our problem: There are no error shown. Before migration, everything worked. With 5.1.2, the login does not work in Blazor Server UI. There is also nothing mentioned in the migration guide regarding this. I dont see a way to find the error with 0 logged exceptions, and no change on our side to the login workflow between abp 5.0.1 and 5.1.2.
1 Answer(s)
-
0
Problem was just chrome not allowing the cookies, so 1.5.2 works!