The mere fact that SkipKit does import CoreLocation is enough to trigger a warning when submitting an app that uses it:
Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect.
ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “Stanza.app” bundle should contain a NSLocationAlwaysAndWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. For details, visit: https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/requesting_access_to_protected_resources.
ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “Stanza.app” bundle should contain a NSLocationWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. For details, visit: https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/requesting_access_to_protected_resources.
Unlike Contacts and EventKit imports, this is not a fatal app submission error, but it is an alarming warning, and might someday be escalated to app review delays or outright rejections.
We should probably add a separate skip-location package, like we did for skip-calendar and skip-contacts to get around this issue.
The mere fact that SkipKit does
import CoreLocationis enough to trigger a warning when submitting an app that uses it:Unlike
ContactsandEventKitimports, this is not a fatal app submission error, but it is an alarming warning, and might someday be escalated to app review delays or outright rejections.We should probably add a separate
skip-locationpackage, like we did for skip-calendar and skip-contacts to get around this issue.