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
My iOS app using moko-permissions was rejected by App Store Connect because Info.plist keys for NSContactsUsageDescription and NSMotionUsageDescription were missing. This happened despite not using these features, as the library implicitly referenced them.
Problem
Unused permissions are included by default, leading to:
App store rejections.
Manual fixes like adding unnecessary Info.plist keys.
Proposed Solution
Explicit Permission Registration
Allow developers to register only the permissions they need:
val permissionsManager =PermissionsManager.create {
registerPermission(Permission.CAMERA)
registerPermission(Permission.LOCATION)
}
Build-Time Validation
Warn if required Info.plist keys are missing or if unregistered permissions are included.
Documentation Update
Guide users on registering permissions and preventing app store issues.
Benefits
Prevents unnecessary permissions in builds.
Avoids app store rejections.
Simplifies configuration and debugging.
The text was updated successfully, but these errors were encountered:
Issue
My iOS app using
moko-permissions
was rejected by App Store Connect becauseInfo.plist
keys forNSContactsUsageDescription
andNSMotionUsageDescription
were missing. This happened despite not using these features, as the library implicitly referenced them.Problem
Unused permissions are included by default, leading to:
Info.plist
keys.Proposed Solution
Explicit Permission Registration
Allow developers to register only the permissions they need:
Build-Time Validation
Warn if required
Info.plist
keys are missing or if unregistered permissions are included.Documentation Update
Guide users on registering permissions and preventing app store issues.
Benefits
The text was updated successfully, but these errors were encountered: