-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android Autolinking #299
Comments
Thank you for requesting this feature! Looks interesting, we are going to look into adding support for this. |
We've managed to get autolinking work when we use Looking at the So I wonder if both are mutually exclusive? 🤔 @Taylor123 do you happen to know if we can support both autolinking and Turbo packages at the same time? Or do we have to choose one or the other? |
I haven't personally used |
I've created a draft proposal that makes autolinking work (at the expense of app startup time). Please chime in with feedback and opinions. |
We've decided to stick to turbo modules for now as faster app initialization outweighs the easier integration (especially on the longer term) In the future we may decide to revise this or to add auto linking support for Turbo Modules. (when that becomes possible) |
@JeroenMols Makes sense, thanks for taking the time to look into this |
The problem
Android auto linking does not currently work.
Environment
react-native config output
Expected Result
android react-native config should not be
null
The text was updated successfully, but these errors were encountered: