[question] Better understanding of what setup-ios-permissions is doing

[raid5]

Why it is needed?

This is more of a question and not a feature request, but I didn't see that option as one of the issue templates. For iOS, I understand that setup-ios-permissions will add the necessary source files to the RNPermissions.podspec by reading the permissions listed in the package.json (or reactNativePermissionsIOS.json). I'm curious why this is necessary and why you can't just always include all of the source files without this step? I'm trying to understand the reasoning for the added setup complexity and the pros/cons of doing it this way.

Thanks!

Possible implementation

No response

Code sample

No response

[zoontek]

On iOS, app store reviewers often reject apps that include code to request unused permissions:

• Denied from appstore #46
• How to remove unnecessary permissions on iOS? #240
• App Rejected in AppStore #266

The approach has been to create a modular package, at first with subspecs, then with a dedicated podspec for each permission. Each "permission handler" includes the check / request code.

It wasn't perfect since it could create a bunch of caching issues, introduce the need for a workaround when using use_frameworks!

To solve this, we switched to a react native CLI command: setup-ios-permissions
It does a pretty simple job: it edits node_modules/react-native-permissions/RNPermissions.podspec source_files to add your selected permission handlers directories.

Another benefits is that permissions handlers are now included in the module pod, not in separated ones:

I hope this answer your question.

[raid5]

@zoontek thanks for the detailed explanation! I really appreciate it and love this library <3