-
Notifications
You must be signed in to change notification settings - Fork 658
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
Does the 0.12 version support autolink? #414
Comments
Same problem here |
I have the same issue, and haven't been able to find a workaround. |
I also tried everything from referenced thread and can’t pass this error on RN60.6 |
Just a small idea for those that need speed like me.
|
@vvusts thank you very much for this workaround. |
Auto linking worked for me but I had to clean up the old settings:
|
@lapto which version of react-native-config did you use ? |
|
@lapto Did you add any post install script in your podfile? |
@jitendralakhmani-proptiger I do have the extra steps described in readme for the android build tho |
@MaxInMoon I managed to autolink with v0.12. Using it with fastlane, I have written up my approach here and repo. |
@vvusts @Dimon70007 what were the steps to link it "manually" in Xcode? |
@grifotv for manual linking module.exports = {
dependencies: {
'react-native-config': {
platforms: {
ios: null, // disable autolinking react-native-config for ios
},
},
},
}; and run |
thanks @Dimon70007 I did like you said, but instead of manually linking I used |
I tried! It work with auto linking:
It also work for ios Info.plist. The README did not mention that I need to change the key:
Follow README file and use $(KEY) form will work |
Please use |
What do you mean "fixed in this version" ? A simple |
I'm wondering if 0.12 version support autolink cause:
First
In the readme there is:
But autolink should not need a link command, right?
Secondly
With these versions:
I have an error on iOS:
See #187 (comment)
The text was updated successfully, but these errors were encountered: