When returning to the site after being on it the previous day, it picks up as not being logged on (which is fine). After going through the log on process, everything comes up fine. However, ~30 seconds from that time, the menu changes back to the non-logged-on version. API calls still work, but something is switching isAuthenticated back to false.
I suspect the issue lies in the refreshTokens function.
When returning to the site after being on it the previous day, it picks up as not being logged on (which is fine). After going through the log on process, everything comes up fine. However, ~30 seconds from that time, the menu changes back to the non-logged-on version. API calls still work, but something is switching `isAuthenticated` back to `false`.
_I suspect the issue lies in the `refreshTokens` function._
Resolved this without code; there is a separate spot in the Auth0 config for which origins are allowed to make these types of requests. I put https://prayerjournal.me in that spot, and the existing code now works.
Resolved this without code; there is a separate spot in the Auth0 config for which origins are allowed to make these types of requests. I put https://prayerjournal.me in that spot, and the existing code now works.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When returning to the site after being on it the previous day, it picks up as not being logged on (which is fine). After going through the log on process, everything comes up fine. However, ~30 seconds from that time, the menu changes back to the non-logged-on version. API calls still work, but something is switching
isAuthenticatedback tofalse.I suspect the issue lies in the
refreshTokensfunction.Resolved this without code; there is a separate spot in the Auth0 config for which origins are allowed to make these types of requests. I put https://prayerjournal.me in that spot, and the existing code now works.