Why is my MAUI/.NET iOS app being rejected by Apple for a 'Missing privacy manifest' (ITMS-91061) related to FBLPromises or GoogleDataTransport?

If your MAUI/.NET iOS application is rejected by the App Store with an error message like ITMS-91061: Missing privacy manifest for frameworks such as FBLPromises or GoogleDataTransport, it is likely caused by a third-party dependency in your project, not the Pushwoosh SDK.

The Pushwoosh .NET SDK for iOS (Pushwoosh.DotNet) does not include FBLPromises or GoogleDataTransport as dependencies. Our SDK already includes the required PrivacyInfo.xcprivacy files.

This issue typically arises when another package in your project has a transitive dependency on an outdated Google or Firebase library (e.g., older Xamarin.Firebase.* packages) that does not contain the required privacy manifests.

How to resolve this issue:

1. Analyze your project's dependencies: You need to inspect your project's complete dependency tree to identify which package is introducing these frameworks. For example, a package for barcode scanning or analytics might indirectly pull in an old version of Xamarin.Firebase.iOS.Core.
2. Identify the source: Look for packages that rely on deprecated libraries like Xamarin.Firebase.*. These have been largely replaced by community-maintained alternatives that include updated Firebase iOS SDKs with proper privacy manifest support.
3. Update or replace the package: Once you have identified the source package, the solution is to:
   • Update it to a newer version that uses compliant dependencies.
   • If an update is not available, contact the package maintainer or find an alternative package that is actively maintained and compliant with Apple's latest requirements.