NSPrivacyAccessedAPICategoryDiskSpace

[jamiehunt]

I have reason to believe the GoogleMobileAds framework is triggering the privacy sensitive API usage alert, while we can work-around this by marking one of the respective NSPrivacyAccessedAPITypeReasons, I don't know that any of the justifications apply for GoogleMobileAds's usage of the API so cannot in good faith make this declaration.

I note that the Firebase Crashlytics 10.22.0 release "removed calls to statfs in the Crashlytics SDK to comply with Apple Privacy Manifests. This change removes support for collecting Disk Space Free in Crashlytics reports".

Can we confirm if there are disk usage related API calls within the GoogleMobileAds framework and that we can get them removed ahead of 1st May when Apple begins enforcing this policy?

Thanks

[machl]

Same here.
GoogleMobileAds is indeed triggering privacy sensitive alert for NSPrivacyAccessedAPICategoryDiskSpace.

Using https://github.com/Wooder/ios_17_required_reason_api_scanner I can see
Used symbols in binary ./Development - Debug-iphonesimulator/GoogleMobileAds.framework/GoogleMobileAds: NSFileSystemFreeSize, NSFileSystemSize, NSUserDefaults

[sarodger]

Any update on this please?

[malandr2]

@ALL

We are aware of the warnings. This is something Apple will have to fix.

[RoblesJ]

To the googleAdds Team,

Thank you for the update.

Just to confirm, are we correct in understanding that your usage of this particular API doesn't necessitate declaration, and that the issue lies with Apple's implementation?

If this is the case, it's imperative that we gather accurate data to substantiate our position. Since we are ultimately responsible for integrating the SDK into our applications, we need to be able to clearly articulate why certain requirements imposed by Apple are not applicable.

Please ensure that we have access to this data in the event that our application uploads are rejected.

Thank you for your attention to this matter.

[ericleich]

Starting in version 11.2.0, the SDK's framework distributes a PrivacyInfo.xcprivacy declaring the usage reasons for these APIs. You can view the declarations by downloading the SDK manually and finding this file. The bug is that App Store Connect is not pulling in those declarations for static frameworks, and think the declarations are missing.