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

Not compatible with RN 0.60 #21

Open
chrisspankroy opened this issue Jul 9, 2019 · 4 comments
Open

Not compatible with RN 0.60 #21

chrisspankroy opened this issue Jul 9, 2019 · 4 comments

Comments

@chrisspankroy
Copy link

chrisspankroy commented Jul 9, 2019

When running pod install on a project in RN 0.60 (master branch) that depends on this library, it fails and this message is printed:

[!] use_native_modules! skipped the react-native dependency 'react-native-open-settings'. No podspec file was found.
    - Check to see if there is an updated version that contains the necessary podspec file
    - Contact the library maintainers or send them a PR to add a podspec. The react-native-webview podspec is a good example of a package.json driven podspec. See
    https://github.com/react-native-community/react-native-webview/blob/master/react-native-webview.podspec
    - If necessary, you can disable autolinking for the dependency and link it manually. See
    **https://github.com/react-native-community/cli/blob/master/docs/autolinking.md#how-can-i-disable-autolinking-for-unsupported-library

I believe #16 will fix this issue. Please merge it

@lodev09
Copy link

lodev09 commented Aug 3, 2019

you don't need this package for RN 0.60. You can now do Linking.openSettings()
See docs

@gabrielrra
Copy link

you don't need this package for RN 0.60. You can now do Linking.openSettings()
See docs

Linking.openSettings() only opens your app's settings, not the phone's.

@twelve17
Copy link

twelve17 commented Jan 9, 2020

Any news on this? Anything I can do to help get #16 merged?

@SethArchambault
Copy link

Yeah I had to fork this and make this change..
Made a pull request, but looks like #16 already resolved this nicely!

#24

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

No branches or pull requests

5 participants