I published to Azure.
The component is displayed and after one second from login it changes its state.
I published to Azure, but now I have a different behavior. https://abpsolution1.azurewebsites.net/
When I log in it sees me as unauthorized and therefore does not call GetBooks for this reason now it does not go into error. Can you test it? Thanks
The solution is published on an on-premise server that is not accessible externally from our client's network. I try to create an environment on Azure and then I'll send you the link
https://github.com/abpframework/abp/issues/20483
Hi, do you think this issue could be related to my problem?
I sent you the logs of browser.
thanks
Ok, but can you explain what that piece of code does?
I sent you the logs from today's test. I tried without the fix and got the error. I added the fix and I don't get the error anymore. Can you explain what that piece of code does? Will this fix be a patch in the next release? Is this fix also compatible with AzureAd login?
Thanks, Roberto
I have sent the requested log Thanks
Not worked for me.
Error:
In console I see a warning:
I debug from Visual Studio with multi-launch project using IIS Express and then log in to the portal. I don't understand why the component is initialized twice and the second time the get passes a wrong token to the api It looks like a token handling issue because the component is in the layout instead of being on a page.
I get the same error if I publish on IIS
Can you try again by also logging out and logging back in? Maybe it's a problem that happens if you already have a token in cache
Thanks
Project sent via wetransfer. Thanks
