Sign up for our live Camera Kit office hour on July 17 @ 9:30am (PT) / 4:30pm (GMT)

Invalid API Reason Declarations in SCSDKCameraKit.framework Causing App Store Rejection

ron kang
ron kang Posts: 1

Hello,
I am currently facing an issue with my app submission to the Apple App Store and need your assistance to resolve it.

My app was rejected with the following errors related to invalid API reason declarations:

The PrivacyInfo.xcprivacy file for Frameworks/SCSDKCameraKit.framework/SCSDKCameraKit contains E174.1 as the value for an NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for the NSPrivacyAccessedAPICategoryFileTimestamp category.
Similar issues were found with CoreResources.bundle/Overlay.lns and LiteTrackingData.lns files within the same framework.
The PrivacyInfo.xcprivacy file for Frameworks/SCSDKCameraKit.framework/SCSDKCameraKit also contains C617.1 as the value for an NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for the NSPrivacyAccessedAPICategoryDiskSpace category.
Similar issues were found with CoreResources.bundle/Overlay.lns and LiteTrackingData.lns files within the same framework.

After reviewing the error details, it appears that the reason codes C617.1 and E174.1 might be used in the wrong contexts. Specifically, C617.1 should be used for NSPrivacyAccessedAPICategoryFileTimestamp and E174.1 should be used for NSPrivacyAccessedAPICategoryDiskSpace.

Could you please look into this issue and provide the necessary corrections for the NSPrivacyAccessedAPITypeReasons keys in the PrivacyInfo.xcprivacy file?

Thank you for your help and prompt attention to this matter.

Best regards,
Ron

Tagged:

Answers

  • I'm facing same issue is there any solution?

    Hello,

    Please correct the following issues and upload a new binary to App Store Connect.

    ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/SCSDKCameraKit.framework/SCSDKCameraKit” file contains “E174.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryFileTimestamp category. Values for NSPrivacyAccessedAPITypeReasons keys in any privacy manifest must be valid reason codes for the corresponding API category. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

    ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/SCSDKCameraKit.framework/CoreResources.bundle/Overlay.lns” file contains “E174.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryFileTimestamp category. Values for NSPrivacyAccessedAPITypeReasons keys in any privacy manifest must be valid reason codes for the corresponding API category. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

    ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/SCSDKCameraKit.framework/CoreResources.bundle/LiteTrackingData.lns” file contains “E174.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryFileTimestamp category. Values for NSPrivacyAccessedAPITypeReasons keys in any privacy manifest must be valid reason codes for the corresponding API category. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

    ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/SCSDKCameraKit.framework/SCSDKCameraKit” file contains “C617.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryDiskSpace category. Values for NSPrivacyAccessedAPITypeReasons keys in any privacy manifest must be valid reason codes for the corresponding API category. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

    ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/SCSDKCameraKit.framework/CoreResources.bundle/Overlay.lns” file contains “C617.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryDiskSpace category. Values for NSPrivacyAccessedAPITypeReasons keys in any privacy manifest must be valid reason codes for the corresponding API category. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

    ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/SCSDKCameraKit.framework/CoreResources.bundle/LiteTrackingData.lns” file contains “C617.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryDiskSpace category. Values for NSPrivacyAccessedAPITypeReasons keys in any privacy manifest must be valid reason codes for the corresponding API category. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

    Apple Developer Relations

  • JacekC
    JacekC Posts: 25 👻

    Hi,
    Thank you for reporting this. Can you please confirm which SDK version you are using? We recently released SDK update to address those issues. It's available in following versions: