Skip to content
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

Play nice with 0.29.2 on both platforms again. #406

Closed
wants to merge 3 commits into from

Conversation

skellock
Copy link
Contributor

Just a few changes to make things work out of the box again.

Android:

  • Changing the build gradle to use the "current" version instead of a specific version. I read in another issue that wasn't the preferred way and that React Native gets it wrong? I'm not sure how to solve this correctly, this works though. I like what's written on the README: we link to the latest version (using *)... this change sort of sees that through.
  • Provides a hint to rnpm (aka react-native link) in package.json to hookup settings to the lib folder directly. Not quite sure why I had to do this. Perhaps it's a standard to live in the android folder? It seems like we have two ways of linking... via source and via maven?

iOS:

  • Fixes two header files which suddenly stops working in the latest React Native.

I hear this is the wrong way to do this.  I'm not sure what the right
way is.  All I know is, without this change, the project doesn't
compile on Android and RN 0.29.2.

Feels wrong to specify the React Native version number in here, when at
the NPM level, we target the "latest" React Native dependency with a *.
@@ -16,7 +16,7 @@ android {
}

dependencies {
compile 'com.facebook.react:react-native:0.29.0'
compile 'com.facebook.react:react-native:+'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has been discussed a lot in other issues, tl;dr: just revert it :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I figured this would be a no go. Is there a way we can make this library survive React Native upgrades without it though?

codenamev added a commit to reenhanced/react-native-maps that referenced this pull request Jul 21, 2016
@skellock
Copy link
Contributor Author

Closing. Addressed in #411.

@skellock skellock closed this Jul 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants