-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NullReferenceException in Volo.Abp.AspNetCore.Components.Web.LeptonTheme.Components.ApplicationLayout.MainHeader.MainHeader #20616
Comments
@EngincanV @maliming no feedback on this? Unfortunatly I can´t create a demo code using the pro version to share with you... |
I have figured out that this only happens when I F5 the page but if I navigate to it by menu this doesn´t happen. 🤷♂️ |
You'd better share a project that can reproduce the problem. This way we can find the cause as quickly as possible |
|
Hey there. I see that this issue is closed but I don't see what was the solution. I'm facing the same problem as shown below. It's weird because the error seems to happen at random (about 50% of the times) when refreshing the login screen. I tried different Blazorise versions without success. I'm on ABP 8.3.2. |
hi I have reproduced the problem. I will fix this in 8.3.3. |
Is there an existing issue for this?
Description
Coming back to a open tab and refreshing I´m getting that error and no amount of F5 fixes the issue. The only thing possible is to clear all application data (totally not something a normal user is expected to do)
The issue seems to be in code handling of "Volo.Abp.AspNetCore.Components.Web.LeptonTheme.Components.ApplicationLayout.MainHeader.MainHeader.Dispose()"
Full log. As you can see the user seem to be no longer with valid credentials.
Then probably because of that error few other errors follow
Reproduction Steps
N/A but you should at least look at the code that is throwing the NullReferenceException and prevent that!
Expected behavior
If the user no longer has valid credentials he/she should be routed to a login page or the a refresh token mechanishm should kick in.
Actual behavior
The page becomes useless!
Regression?
First time I´m seeing this after updating to 8.2.x
Known Workarounds
Nuke the application data in the browser.. not viable
Version
8.2.2
User Interface
Blazor Server
Database Provider
EF Core (Default)
Tiered or separate authentication server
Tiered
Operation System
Windows (Default)
Other information
I sure hope you harden this code part in 8.2.3!
The text was updated successfully, but these errors were encountered: