And I did note that after some time idle, the app stop to work but it doesn’t raise any error, only showing the message that show the info that the server is unavailable…
I did note that in the browser console, it is showing the following warning/error:
Error description
Access to fetch at ** < LINK > **** (redirected from ‘http://localhost:8050/_reload-hash’) from origin ‘http://localhost:8050’ has been blocked by CORS policy: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.
I would like to know if someone has faced this problem before or if someone knows how to deal with it... I did some searches and tried some approaches but I do not have any idea on how to solve the problem.
Any help on how to debug it will be really appreciated.
I found a snippet code that I have adapted with your suggestion… I’m not sure if it will work, but if it works or not I will update this thread with the answer
Looking at this again, it seems as if it might be an issue with the redirect.
Is it possible to handle the refreshing of the token on the server side instead of on the client?
This could also be an issue with the registry of the application on the azure side as well. The urls I think should be updated for where they will redirect to, not a localhost, but the full hosted web address?