Improved privacy manifest and client debug data
We have released new patch versions 3.16.4, 3.17.3, and 3.18.3 for our iOS SDK.
Patch overview
- Added
PrivacyInfo.xcprivacy:- As of 01.05.2024, Apple has enforced apps to describe their use of the required reason API in their privacy manifest file.
- The article Describing use of required reason API in the Apple developer documentation warns:
If you upload an app to App Store Connect that uses required reason API without describing the reason in its privacy manifest file, Apple sends you an email reminding you to add the reason to the app's privacy manifest. Starting May 1, 2024, apps that don't describe their use of required reason API in their privacy manifest file aren't accepted by App Store Connect.
- If you are using Xcode 15, embed the Encap framework that was dragged in. Navigate to the target's General settings, locate Frameworks, Libraries, & Embedded Content, then select Embed & Sign. This step will enable privacy manifests to be picked up by Xcode's tooling.
- Removed
diskSpace:- In versions 3.16 and above,
diskSpaceis no longer available in our client debug data feature. - This update became essential when reviewing our data usage, particularly for
NSPrivacyAccessedAPICategoryDiskSpacewhere the available options did not accurately reflect our circumstances. - In alignment with Apple's guidelines, we have chosen to entirely remove references to diskSpace APIs.
- In versions 3.16 and above,
Affected versions
If your app uses an affected version of the SDK, then you should upgrade it to use the latest, patched version:
| Affected versions | Patched version |
|---|---|
| 3.18.2 | 3.18.3 |
| 3.17.2 | 3.17.3 |
| 3.16.3 | 3.16.4 |
| Earlier versions | N/A |
How to upgrade
For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.
To learn how to do this, see our Upgrade guide.
If this is not possible, see section Known limitations and workaround below.
Known limitations and workaround
We have seen that declared use of the reason API in the PrivacyInfo.xcprivacy file inside the SDK is not getting taken into evaluation from Apple when sending the app to the App Store for review. We have an ongoing support ticket with Apple and currently assume that it is a bug on Apple's side.
If you experience this problem, we suggest that you take what we have declared in the PrivacyInfo.xcprivacy file, and add to your PrivacyInfo.xcprivacy file until this issue is resolved.
If you are using an SDK below version 3.16, then the PrivacyInfo.xcprivacy found in newer versions can be used and copied across. In this case, it is expected to be in the root of the .framework folder for both architectures.
You can download the library from our Nexus partner repository. Change your current dependency to the new version.