This is a follow-up for #4363 and #4503.
First I want to mention that my application is closed to be deployed in PROD. So I cannot just start over with other tech stack.
The application is fully updated with latest ABP Nuget and NPM packages and its deployed to Azure.
The problem is that ICurrentUser, or AuthState is not available after login, only after the page is refreshed.
This in turn affects if the menu is rendered or not. In my case I need to display some menus / submenus based on various roles or other user related properties.
In the first ticket opened it was a problem with the LeptonXTheme. I was instructed to wait for 2.0 release and it will work. Didn't work.
I also shared the project with the support team, but to no avail. Last recommendation was to publish a new blazor wasm template to Azure. I cannot do that as I am in the process of delivering it.
My question still stands: why I don't get the current user after the login in the menu contributor and why after the page refresh is working and why on local dev is working? Do the tech guys managed to publish a Blazor WASM app to Azure and reproduce this? It is the most frustrating problem I ever encountered.
I really need help. I can share the solution to inspect it again.
Tks a lot!
I confirm that now it works.
Thank you.
Hi,
I update all ABP Packages from ABP Suite for both Blazor Server and Blazor wasm projects.
It seems that the problem with Top Menu rendering is OK, but now I get this:
In Blazor WASM I hit this as soon as I hit login.
In Blazor Server it comes directly when I try to run the app.
Just to be clear: 7.1.0 on ABP Packages.
Tks a million!
PS: If you found this is a bug, please do not count this question towards my allotted max support questions. :)
hello!
I created a new app, no layers, blazor server, changed top menu and got the error. If I switch back to Side Menu, its working.
I don't think it is bundle related.
Also for my original project, yes, I ran the abp bundle. No change.
Hi, Support!
Any updates?
Hi, SupportTeam!
First of all, I hope you will all recover from the devastating loss and pain brought on by the earthquake. I also hope you and your loved ones are OK. I am so very sorry.
I have a project inside an ABP Framework solution which is an API client to access an external API. From the get go, any test did with Postman is working correctly.
Structure:
Module file:
Extension file:
The rest are related to the API itself - models, client, etc.
The services are properly initialized. I can inject them with no problem in any page on the frontend.
But I always get the same error:
The server doesn't have CORS policies, and any test with something different than ABP works.
What am I doing wrong? Any tips would be appreciated.
Thanks, Catalin
hi
did that, no success. :( as I mentioned, on local dev, all OK.
deployed to Azure, it doesn't. page needs to be refreshed after user logs in in order for the menu to render.
in the blazor frontend I needed to to some modifications to these:
I don't know if these modifications (minor things) are causing this behavior when deploying to Azure.
can I share the project with you?
in the original thread I've provided some test credentials to see the behavior on-line.
Hello,
This is a follow-up of bug #4363. The issues should have been solved with the 2.0 LeptonX patch, but, unfortunately, it isn't.
Can you please advise further?
Tks a lot!
Tks! Closing!
LE: I updated all my packages to 2.0.1 LeptonX, but still have the same problem: menu is not rendering when user logs in, I still have to refresh it.
