pamapa
pamapa
@jantari You saved my day, thanks for sharing!
I am not so sure if its worth all the additional dev dependencies, e.g. release-it can do much more, which we do not need...
- `addUserSignedIn`, `addUserSignedOut` and `addUserSessionChanged` only work in combination with `SessionMonitor` - `addAccessTokenExpiring` and `addAccessTokenExpired` are fired when the access token has nearly expired, that may take serveral hours until...
> What do you mean with "only work in combination with `SessionMonitor`"? When can I find an example Those event are only raised in the `SessionMonitor`, as such that monitor...
Is this what you want to achieve? https://github.com/authts/react-oidc-context/blob/main/src/AuthProvider.tsx#L169
Are you using ReactStrict mode with `react-oidc-context`?
Are you affected by https://github.com/authts/react-oidc-context/issues/390. I assume we need to add something for this mode to work properly. Does it work without that mode?
`_raiseUserSessionError` is never called. What is the difference to `_userSessionChanged`. Why can't you use that one?
Are you using silent renew with refresh token or without? With refresh token: In this case fetch is used. See `exchangeRefreshToken` here https://github.com/authts/oidc-client-ts/blob/main/src/TokenClient.ts#L109. This code is using `postForm` in https://github.com/authts/oidc-client-ts/blob/main/src/JsonService.ts#L122....
You will need to debug that on your side. Check if you have a cookie, verify its settings. Verify that the browser is allowed to send it to the request...