cache client instances in Auth0ClientFactory to prevent duplicate state#1506
Merged
subhankarmaiti merged 1 commit intomasterfrom Apr 9, 2026
Merged
cache client instances in Auth0ClientFactory to prevent duplicate state#1506subhankarmaiti merged 1 commit intomasterfrom
subhankarmaiti merged 1 commit intomasterfrom
Conversation
NandanPrabhu
approved these changes
Apr 9, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds instance caching to
Auth0ClientFactory(both native and web) so that multiple calls tocreateClient()with the samedomain|clientIdreturn the sameIAuth0Clientinstance.Problem
When
Auth0Providerunmounts and remounts (e.g., navigation changes, React Suspense boundaries, or Fast Refresh), a brand-new client was created each time. This could lead to:Auth0class singleton and theAuth0ProviderhookVerification
Auth0class andAuth0Providernow resolve to the same underlying client when configured with matching domain/clientId, ensuring credentials saved via one path are immediately visible to the other.