s.static_framework = true hardcoded in podspec forces static linking, causing ITMS-91064 App Store rejection

[ruben-dc]

SDK Version

react-native-appsflyer 6.15.1

Problem

The podspec unconditionally sets s.static_framework = true, which forces AppsFlyerLib to be linked as a static library. When integrated via CocoaPods in a React Native project, this results in the privacy manifest being shipped as AppsFlyerLib_Privacy.bundle/PrivacyInfo.xcprivacy rather than inside a .framework bundle.

Apple's ITMS validator does not correctly process privacy manifests from static library bundles, which causes a persistent ITMS-91064 rejection from App Store Connect:

"Invalid privacy manifest — your app's PrivacyInfo.xcprivacy does not include required entries."

Root cause

react-native-appsflyer.podspec hardcodes:

s.static_framework = true

There is no supported flag or configuration option to override this. Switching to AppsFlyerFramework/Dynamic (which ships its manifest inside a proper .framework) is not possible because the podspec hardcodes the static subspec — consumers would need to fork the plugin to change it.

Expected behavior

Either:

• Allow consumers to opt into dynamic linking (e.g. via a flag or by supporting the Dynamic subspec), or
• Ensure the static library's privacy manifest is validated correctly by Apple's toolchain

Impact

Apps using react-native-appsflyer via CocoaPods are blocked from submitting to the App Store due to ITMS-91064 rejections that cannot be resolved without forking the plugin.

[github-actions]

👋 Hi @ruben-dc and Thank you for opening this issue.
Please contact AppsFlyer support through the Customer Assistant Chatbot for assistance with troubleshooting issues or product guidance.
To do so, please follow this article.