Hi,
Because the Blazor Server and the Blazor WebAssembly is different, The details may be different when writing UI code, so ABP has created separate projects for them
For example, you can inject IHttpContextAccessor in the Blazor server UI, but it's not available in Blazor WebAssembly.
Hi,
The Module code is no problem, and as you said it works locally.
Could you add the following code to your module class(AuthServer and HttpApi.Host) :
Microsoft.IdentityModel.Logging.IdentityModelEventSource.ShowPII = true;
Change your logging level to debug, then redeploy and share the logs.
BTW, could you share the Txt file instead of CVS? thanks.
That means I will create a sample : ), you can follow the issue
https://learn.microsoft.com/en-us/dotnet/api/system.int32.maxvalue?view=net-8.0
Int.MaxValue is 2147483647. I don't know why you have to return so much data. You may need to reconsider your use cases. : )
: )
Hi,
Ok, I will make an example for you: https://github.com/abpframework/abp/issues/18474
: )
Hi,
I didn't see any ProcessAuthenticationContext was marked as rejected by OpenIddict.Validation.OpenIddict message in the logs.
Could you share the full log file both Authserver and HttpAPI.Host? thanks.
Sadly, it sounds like no one is actively working on this bug as its been unresolved for over 4 months now, and new releases have come and gone. This is rather disappointing as its a commercial module that we've paid for through license fees and it appears that we now have to abandon the LeptonX theme as the bug seems unavoidable when using Blazor. Can you offer us any workaround? or is this bug considered unfixable or not worth the effort of fixing for whatever reason?
Sorry for that, I will reconsider this question and try to find a way.
This is the temporary solution: https://support.abp.io/QA/Questions/6126/CSS-delay-loading-and-the-UI-would-flash#answer-3a0efc85-ee1a-266f-cfc5-aad1337e3227
Hi,
Sorry, I could not open the link. could you send log via email?
