You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I received this warning when I recently submitted an app that uses ClusterPrePermissions from the app store:
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSCalendarsUsageDescription key with a string value explaining to the user how the app uses this data.
I'm not using the Calendar permissions at all, I'm only using microphone permissions.
The text was updated successfully, but these errors were encountered:
It seems like the Apple app store code analysis is seeing the use of EKEventStore within the ClusterPrePermissions library and rejecting the app unless I include the NSCalendarsUsageDescription in the Info.plist.
Switch each permission into a separate CocoaPod subspec, or
Rewrite this library in a way to genericize some the repeated flows.
The problem with (1) is that it makes the code ugly, and adding new permissions will continue to be hard/unmaintainable. The problem with (2) is the extra cognitive load of managing the pods.
Solution (3) is the ideal one, I think. Especially given that the library is still using UIAlertViews and all. A Swift-based solution might help tremendously, with typed enums and enums with associated values.
I received this warning when I recently submitted an app that uses ClusterPrePermissions from the app store:
I'm not using the Calendar permissions at all, I'm only using microphone permissions.
The text was updated successfully, but these errors were encountered: