Skip to content

Update RNCallKeep.podspec #69

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

Closed
wants to merge 1 commit into from

Conversation

anhtuank7c
Copy link
Contributor

Fix React Core for RN 0.60.3

Fix React Core for RN `0.60.3`
@@ -13,6 +13,6 @@ Pod::Spec.new do |s|
s.requires_arc = true
s.platform = :ios, "8.0"
s.source_files = "ios/RNCallKeep/*.{h,m}"
s.dependency 'React/Core'
s.dependency 'React-Core'
Copy link
Contributor

Choose a reason for hiding this comment

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

Merging this will mean 0.60 is the minimum version of React Native supported, right? Unless we can come up with a way to set this based on the react-native dependency's version, this will have to wait. There's too many parts of the matrix to require Call Keep users to move all the way to 0.60 now.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah, minimum rn 60+

Copy link
Contributor

Choose a reason for hiding this comment

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

I think this needs to hang out a while then, maybe in a beta tagged branch @sboily? The dependency ecosystem is too complex to push to 0.60 as a minimum at this point.

Copy link
Member

Choose a reason for hiding this comment

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

Yes we can't do that fo the moment, react-native 0.60 is too young and we have a major risk to broke many applications. I'm open to have branch or other solution for people want to have 0.60+.

Copy link
Contributor

Choose a reason for hiding this comment

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

I tried with s.dependency 'React'. It works just fine with RN 0.60.5. So I think it can work for RN <0.60 too.

Copy link
Contributor

Choose a reason for hiding this comment

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

@Robot

I tried with s.dependency 'React'. It works just fine with RN 0.60.5. So I think it can work for RN <0.60 too.

That's still trying 0.60+... What about with 0.5X?

Copy link
Contributor

Choose a reason for hiding this comment

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

@kylekurz It should work with 0.5x. Because React is a base library for all.

pod 'React', :path => '../node_modules/react-native'

Copy link

Choose a reason for hiding this comment

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

Please, merge with pod 'React', :path => '../node_modules/react-native'

@danjenkins
Copy link
Collaborator

So will React or React-Core work for 0.59 ?

@jpotts18
Copy link
Contributor

jpotts18 commented Nov 13, 2019

Quick 1-liner (tested on Mac)
sed -i.bak 's/React\/Core/React-Core/g' ./node_modules/react-native-callkeep/RNCallKeep.podspec

@danjenkins
Copy link
Collaborator

Based on repos in react-native-community we can indeed just use React https://github.com/react-native-community/react-native-device-info/blob/master/RNDeviceInfo.podspec

@podvipodvert
Copy link

What’s progress on this?

@manuquentin
Copy link
Contributor

manuquentin commented Dec 2, 2019

Superseded in #135.

👉 3.0.8

@manuquentin manuquentin closed this Dec 2, 2019
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.

9 participants