fix: make DataStore a singleton to prevent IllegalStateException on Android - #793
Open
gcoro wants to merge 1 commit into
Open
fix: make DataStore a singleton to prevent IllegalStateException on Android #793gcoro wants to merge 1 commit into
gcoro wants to merge 1 commit into
Conversation
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
1 participant
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.
DataStorePrefsStorage creates a new DataStore instance via the preferencesDataStore delegate every time KeychainModule is instantiated. Since Android's DataStore enforces a single-instance-per-file constraint, this was firing the following exception on version 10.0.0 when the module is recreated
In this PR I replaced the preferencesDataStore property delegate with a companion object singleton using double-checked locking. The DataStore instance is created once via PreferenceDataStoreFactory.create() and reused across all subsequent KeychainModule instantiations.
This should fix issue #777 and #784.
I tested this fix on my app running RN 0.81.5 and new architecture.