-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
onSuccess is called twice #75
Comments
Same for me |
i am having same issue plz help |
By any chance the component hosting the hook is getting rendered twice? or can you provide some more context on the usage? |
I had the same issue in development due to <React.StrictMode> |
@kallsbo |
Same issue coming for me! |
Removing <React.StrictMode> works but how onSuccess is getting triggered second time and there should be some solution for this |
I am having same is there any solution to that apart from removing StrictMode |
Good day @gauravp-dev , did you get a solution to this? I am currently experiencing the same issue |
I have the same issue, any suggestions besides removing strict mode? |
When I get the authorization code from the onSuccess callback, I will try to retrieve an access token from LinkedIn. However, I found that the
onSuccess
callback is always called twice with the same authorization code. It will trigger my function to LinkedIn twice causing LinkedIn to return an error saying my authorization code is expired in the second call.Is it intented?
The text was updated successfully, but these errors were encountered: