Expired Token Handling
React SDK. To many of the errors are hidden behind console.logs making it impossible to deal with. We also don't need a console log when a token is valid. Currently when a token is expired there is no way to deal with this error making the user journey quite bad.
Also a way to refresh a token would be nice too. I have used many auth libraries before but this one feels unfinished currently. Its also very hard to develop with because when you refresh you lose auth and yes there is the isDangerouslyUseLocalStorage which was working but since the last few updates its now forcing me to do a login every time.
3 Replies
Thanks for the feedback on the console log printing, I will pass this along to the team member who takes care of the SDK to help improve this.
We have just rolled out functionality to refresh the token in our NextJS SDK, so I will get back to you if the React SDK has that yet. Have you set up your custom domain with Kinde? As that will help with token stage in the auth state.
Not yet as I haven't released to production.
I have the same issue in the Javascript SDK https://github.com/kinde-oss/kinde-auth-pkce-js. It could be awesome if you could make a method where it is possible to refresh the token silently.