Privacy Manifest file is missing for FirebasePerformance
Description
When updating to version 10.22.0 of the Firebase Performance SDK, it seems that the manifest file for this SDK is missing. Additionally, the SDK uses "NSUserDefaults" API for some specific reason which requires a manifest. https://developer.apple.com/documentation/foundation/nsuserdefaults
Reproducing the issue
No response
Firebase SDK Version
10.22.0
Xcode Version
15.0
Installation Method
CocoaPods
Firebase Product(s)
AB Testing, Analytics, Authentication, Crashlytics, Installations, Messaging, Performance, Remote Config
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand Package.resolved snippet
Replace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand Podfile.lock snippet
Replace this line with the contents of your Podfile.lock!
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
Thank for reporting. Firebase 10.22.0 only published manifests for SDKs named by Apple on this list. We're still working on the Firebase SDKs that are not on that list.
@ncooke3, Is Firestore using any API listed on NSPrivacyAccessedAPICategoryFileTimestamp?
Hi @jesus-mg-ios, no–– not in the latest release.
@ncooke3 Thanks for the input. Do you know if there is an issue or a PR to keep track of progress? I am a user of FirebasePerformance library and want to check in if the privacy info is indeed needed for it and if we could somehow get notified of the progress.
Are folks on this thread using package managers other than CocoaPods? And, if you are using CocoaPods, are you using use_frameworks! or use_frameworks! :linkage => :static in your Podfile?
I'm using Swift PM on my end (via Xcode's package dependencies)
@ncooke3 I am using CocoaPods with use_frameworks! in the podfile.
@ncooke3 using CocoaPods with use_frameworks! in the podfile.
@ncooke3 Any updates on this? Thanks!
10.25.0, due out the week of April 29th, will eliminate the usage of required reasons in FirebasePerformance. See #12759