-
-
Notifications
You must be signed in to change notification settings - Fork 836
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
WIP: 2.0.0 #291
WIP: 2.0.0 #291
Conversation
@zoontek I am really happy to find this pull request, waiting for the new version. Just a side note after I installed the new version yesterday: after some hours of trying to make it work on iOS, I realized that My Podfile looks somehow like this:
|
@bencergazda Thanks, I edited the PR! The CocoaPods install for React is currently discuted here: react-native-community/discussions-and-proposals#96, I hope better officiel documentation will come about it. |
@zoontek One more feedback: just wanted to submit a new iOS build to TestFlight, but it was rejected with a Missing Purpose String in Info.plist File warning. App Store asks for a I am using Here's my Podfile configration:
|
@bencergazda If you don't install the subspec 'Microphone', microphone access code request is not included in your code. Looks like more an issue with That's precisely why this new version of |
@zoontek Indeed, thanks for investigating this! |
how to install version 2.0.0 on npm? |
@nghiatv It's not on npm yet. Maybe should I write basic documentation and publish it as |
@zoontek I think it really deserves an alpha state. One more thing: after clean
The two affected lines: Replacing
in both lines to
fixes the error. |
If you have something almost stable, an alpha could be great to be able to allow permissions on RN 0.52+ |
Amazing work. I'm looking to use it in a new project, any idea when this beauty will be released @zoontek ? |
@kaueDM You can already install the RC1, but expect the final version next week 😏 |
If you struggle understanding the permission flow, I made some flowcharts: https://github.com/react-native-community/react-native-permissions/blob/2.0.0/README.md#understanding-lifecycle |
That is ace @zoontek ! |
@zoontek Curious if it's possible / feasible to detect the status of these settings for Face ID / Touch ID on iOS: These are likely just OS-specific settings and unavailable to sandboxed apps, but am curious whether these are available as currently it doesn't appear possible to detect whether a user has disabled Face ID / Touch ID on their iOS device, only whether it is How would one detect whether Face ID / Touch ID is " |
@petekp I will check but it will not be my top priority (testing, DX, ecosystem adoption will be)! For everyone here following this PR progression for a few months, I'm honored to say that it has been shipped! 🎉 I also close a bunch of issues / PR which are not relevant since it is out (sorry for that, but I had to cleanup… If the issue is still here, don't hesitate to open a new one on the same subject!) P.-S.: I added a Sponsor button on the repository (only PayPal for now, I will switch to GitHub Sponsor when I'll have access to it). If you use this on a professional project and think it's good work and save you a huge amount of time / money, consider supporting it! 🙂 P.-S. 2: I am still looking for new members / collaborators on the project! 😅 |
Hey @zoontek did you use something to gen these flow charts they are dreamy 🤩 Sorry to bump an old thread but i didn't want to create a new issue just for a qq. |
Hello everyone ! 🙂
As you might know, Apple will now reject your app if your code contains unused permissions request code / usage descriptions (#240)
I started working on a 2.0.0 to tackle this problem, using CocoaPods subspecs.
A full example is available here: https://github.com/yonahforst/react-native-permissions/tree/2.0.0/example
It also have Android native code: we now supports
unavailable
result andopenSettings()
is back!Current API:
How does it works?
RESULTS.DENIED
(you can access the wanted ressources since it's not required yet)RESULTS.UNAVAILABLE
Never ask again
box, results will still be equals toRESULTS.DENIED
, if he checks it, the result will be equals toRESULTS.NEVER_ASK_AGAIN
.RESULTS.NEVER_ASK_AGAIN
(since it can't be ask again in the app, the user will have to open settings to change the permission value)RESULTS.GRANTED
OK, now what ?
I need you help to :
dangerous
android permissions to the list: https://github.com/yonahforst/react-native-permissions/blob/2.0.0/index.js#L17Thanks in advance everyone, let's ship this thing ! 😃
Edit: I would be nice to transfer this repo to the
react-native-community
since @yonahforst does not seems to be active here anymore. A bunch of new collaborators could be a good thing.