-
-
Notifications
You must be signed in to change notification settings - Fork 801
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
[Question]: Notice on iOS permissions and App submission - Still a thing? #1170
Comments
Hello @landliebe, Thank you for submitting this question. I have looked at the documentation and see where your confusion is coming from. I have labelled this issue with the "type: documentation" label, so we can improve on it. However to answer your question: Since version 8.0.0 of the permission_handler plugin we changed the default behaviour on how permissions are used. Before version 8.0.0 all permissions where included by default and you'd have to explicitly disable all permissions your app didn't need. Since version 8.0.0 the permission_handler by default excludes all permissions and developers only have to enable those that the app really needs. Enabling permissions is still done using the pre-processor definitions in the I hope this answers your question, please feel free to leave a comment if you still have additional questions regarding this topic. |
Hello,
In the current Readme following is stated:
Only this part is striked through without any further information why it is striked through:
I checked SO, issues and so on. This was definitely a problem in the past. But is it still? The prepocessor entries in the Podfile: Do they solve this problem, as they prevent the compilation of the unused code for the unused permissions?
If this was fixed with the Podfile entries: It would really help to very clearly state that the "Important: " Notice is not only striked through but also commented like "This was a thing before version x.y.z. This is solved now because of ABC. This information is only still here because ASDF"
Version
11.0.0
The text was updated successfully, but these errors were encountered: