You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apple recently announced a new requirement stating that third-party SDKs utilizing platform APIs must include PrivacyInfo.xcprivacy in their packages for iOS integration. Given Mixpanel's integration with iOS platforms, it's important to address this requirement to ensure compliance.
I would like to inquire whether Mixpanel intends to include PrivacyInfo.xcprivacy in its Flutter package for iOS. Could the Mixpanel team provide insights on whether this addition is necessary or if there are any plans to incorporate it in the future?
Your clarification on this matter would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
So the latest mixpanel_flutter package already have the privacy file included. I have consulted with the mixpanel team and they said to switch to ios sdk 4.2.3 or higher. And in latest version of mixpanel_flutter they uses 4.2.5 ios sdk.
It's just that can't switch to latest versionn due to package constraint upgrade js to 0.7.1#138. In my project many other packages like google_mobile_ads, google_maps_flutter etc uses js below 0.7.1 causing conflicts.
It will be great if the mixpanel team can approve the pr #142
Apple recently announced a new requirement stating that third-party SDKs utilizing platform APIs must include
PrivacyInfo.xcprivacy
in their packages for iOS integration. Given Mixpanel's integration with iOS platforms, it's important to address this requirement to ensure compliance.I would like to inquire whether Mixpanel intends to include
PrivacyInfo.xcprivacy
in its Flutter package for iOS. Could the Mixpanel team provide insights on whether this addition is necessary or if there are any plans to incorporate it in the future?Your clarification on this matter would be greatly appreciated.
The text was updated successfully, but these errors were encountered: