docs: troubleshoot 'QuickBase64 could not be found' (New Arch requirement)#1063
Merged
Conversation
…ment) react-native-quick-base64 3.0.0+ is a pure C++ TurboModule that only registers under the New Architecture. As a required dependency of react-native-quick-crypto, it crashes the app on launch when the consuming app runs on the Old Architecture. Document the cause and the fixes (enable New Arch + clean rebuild, or pin quick-base64 2.2.2). Closes #1052
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Documents the
TurboModuleRegistry.getEnforcing(...): 'QuickBase64' could not be foundcrash reported in #1052.The error originates in
react-native-quick-base64, a required dependency ofreact-native-quick-crypto. As of3.0.0,react-native-quick-base64is a pure C++ TurboModule that only registers under the New Architecture (it has no Old Architecture registration path). Sincereact-native-quick-crypto1.ximports it at startup, an app running on the Old Architecture crashes on launch.This is a documentation fix. No runtime change is required in
react-native-quick-crypto: the requirement is inherent to targeting the New Architecture. The upstream from-source build bug and README note were handled separately in craftzdog/react-native-quick-base64#55.Changes
QuickBase64 could not be foundsection to.docs/troubleshooting.mdcovering:react-native-quick-base64@2.2.2for Old Architecture apps.ndkVersionpatch targets the old2.2.2build.gradleand does not apply to3.0.0.Testing
Docs only. Verified upstream that
react-native-quick-base64registers and passes its suite (36/36) under the New Architecture on Android.Closes #1052