Fixes runtime error where module is null#93
Merged
tectiv3 merged 1 commit intotectiv3:developfrom Dec 4, 2024
Merged
Conversation
tectiv3 added a commit that referenced this pull request Dec 4, 2024
Mia (1): Fixes runtime error where module is `null` (#93) tectiv3 (1): Bump version
Owner
| Thank you! |
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
2 participants
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.
Solves runtime issue where
NativeModules.Aesisnullon Android as reported by #92 and #89.NativeModules.RCTAesseems to work as expected on Android using RN 0.76 (with Expo 52, Turbo Modules and Fabric enabled), and also on iOS.