Support bridgeless mode #57
Merged
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
cortinico
approved these changes
Mar 1, 2024
LinusU
force-pushed
the
support-bridgeless
branch
from
df37541 to
a649360
Compare
|
Thanks for the PR! 🙏 Released as 🚢 1.11.0 / 2024-03-06 |
High5Apps
added a commit
to High5Apps/organize-rn
that referenced
this pull request
Feb 11, 2025
- The warning appeared when creating a new current user - The fix was included in react-native-get-random-values@1.11.0 - LinusU/react-native-get-random-values#57 ``` Warning: Keys.ts:59 Using an insecure random number generator, this should only happen when running in a debugger without support for crypto.getRandomValues ```
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.
global.nativeCallSyncHookis always undefined in bridgeless mode. @tido64 / @cortinico recommend using theRN$Bridgelessglobal to detect bridgeless (although the preference is to not fork behavior based on the new architecture/bridgeless, in this case in order to continue to support remote debugging in older projects in this codebase it makes sense).