Navigator locks are now aquired with a random/unique key. #546
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.
This PR resolves an issue related to sequential
connect()
calls breaking all syncing and never reaching aconnected
state.Two typical scenarios that can cause this is switching client parameters and React's
StrictMode
which does multiple calls of hooks likeuseEffect
.This PR ensures that locks used for internal connection sharing are unique.
Alternative to #545
Thanks @simolus3 for suggesting this approach.