ABP Framework version: v5.1.2
UI type: Blazor Server
DB provider: EF Core
Tiered (MVC) or Identity Server Separated (Angular): no
Steps to reproduce the issue:
This is a bad problem! We have "stand alone" webview pages that are part of a mobile application & require a login & then show 1 view. Now the user gets redirected to a different page, breaking the whole application workflow!
This is probably related to
I hope this can get highly prioritized.
We added ~10 settings pages. Now clicking on "Settings" in "Administration" is taking 10 seconds. It seems like ABP is loading and rendering all settings for all subpages in one go. This should not be done, its not extenable.
How can be tell ABP to lazy load the settings tabs, only when clicked?
One thing we tried was loading the the data itself in OnAfterRenderAsync for each component, but this does not help, as it still does this for all settings at the same time.
All other pages redirect to login. http://localhost:5000/setting-management crashes. This should be fixed.
Problem was just chrome not allowing the cookies, so 1.5.2 works!
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.
This fix will be included in the next 5.0 patch, right?
It seems like today all issues linked to this patch have been solved, is there an approximate release date?
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware: 10:04:36,029 ERROR Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware - An unhandled exception has occurred while executing the request.
Microsoft.AspNetCore.Routing.Matching.AmbiguousMatchException: The request matched multiple endpoints. Matches:
/_Host
/_Host
at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.ReportAmbiguity(CandidateState[] candidateState)
at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.ProcessFinalCandidates(HttpContext httpContext, CandidateState[] candidateState)
at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.Select(HttpContext httpContext, CandidateState[] candidateState)
at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.SelectAsync(HttpContext httpContext, CandidateSet candidateSet)
at Microsoft.AspNetCore.Routing.Matching.DfaMatcher.SelectEndpointWithPoliciesAsync(HttpContext httpContext, IEndpointSelectorPolicy[] policies, CandidateSet candidateSet)
at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.<Invoke>g__AwaitMatch|8_1(EndpointRoutingMiddleware middleware, HttpContext httpContext, Task matchTask)
at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.RequestLocalization.AbpRequestLocalizationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next)
at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>c__DisplayClass6_1.<<UseMiddlewareInterface>b__1>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
We have a blazor server application. After upgrading from 4.3.X to 5.0.1 we now get a AmbiguousMatchException when calling any path directly that is not the root (e.g. http://localhost:5000/audit-logs). Refreshing the root http://localhost:5000, works fine.
In the migration guide and also when comparing the startup templates, I did not see any changes to modules that we also have to do and that can cause this issues.
How is it possible to change the retry count of specific jobs?
With hangfire, this attribute can be used: [AutomaticRetry(Attempts = 0)]. But it doesnt seem to work with ABP. We need different retry attempt counts for each job.
"this is not possible with the known methods right now" says Microsoft developer. See this comment https://github.com/dotnet/aspnetcore/issues/37728#issuecomment-948511840
We do not need the IP addresses.
We just need something to be able to use the auditlogs. E.g. the app-service name that was called. There needs to be something that can be used for filtering.
ip address from http. Example from blazor serv
Hi, How did you achive this on blazor server?