Nan

Hi everyone, since you are using one of our cross-platform SDKs, this is a misleading error message that prints from the integration of our cross platform SDK with our native...

Hi @Nav-3299 thank you for reporting. Can you share what dependencies your `OneSignalNotificationServiceExtension` contains and what code it contains? Also, the OneSignal iOS SDK does not contain any `NSPrivacyAccessedAPICategoryFileTimestamp` APIs....

A followup question for anyone encountering this, can you confirm you are not using `UserDefaults` or the [File timestamp APIs](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api#4278393) in your own source code in your Notification Service Extension?

Hi @Nav-3299 - `OneSignalExtension` framework does not use any `NSPrivacyAccessedAPICategoryFileTimestamp` APIs. - It does use `NSPrivacyAccessedAPICategoryUserDefaults` and it is documented in the Privacy Manifest. I would confirm your FirebaseMessaging dependency...

Hi @Nav-3299, thank you for following up, The warnings are for `OneSignalNotificationServiceExtension`. Please note that `OneSignalNotificationServiceExtension` is just the name for your app's own Notification Service Extension. You could name...

@lobanovD Can you share all your dependencies your Notification Service Extension uses? Additionally, confirm your own code is not calling those APIs?

Hi @lobanovD, > Removing OneSignal from the project solves the problem of submitting the build to the App Store, but this is clearly not the solution I need. When you...

Hi @lobanovD thank you for following up, your error about code signatures is different than the Privacy Manifest APIs reported by Nav-3299. I believe you are using Swift Package Manager....

Hi @lobanovD, the way the sources for the SDK are packaged, the privacy manifests will not show up in the file hierarchy. You can generate your App's privacy report by...

@lobanovD We just released [Release 5.2.0](https://github.com/OneSignal/OneSignal-iOS-SDK/releases/tag/5.2.0) in which we added Privacy Manifests to all of our sub-packages as well. This may resolve the issue for you, can you try?