search

AppLovin / AppLovin-MAX-SDK-iOS

84 stars 69 forks source link

Privacy Manifest being ignored by AppStore #304

Open x3mpablom opened 1 month ago

x3mpablom commented 1 month ago

MAX SDK Version

12.3.1

Device/Platform Info

Any

Current Behavior

When uploading and sending to review a build with Max, we get the following warning from Apple:

ITMS-91053: Missing API declaration - Your app’s code in the “Sample” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code.

We tested this with an app that is not using UserDefaults, and that only the AppLovin sdk is. We know AppLovin is adding the PrivacyInfo.xcprivacy in its bundle (we actually double checked by opening the app inside the archive) but it appears that Apple ignores the privacy manifest.

Expected Behavior

We were expecting no warnings when uploading.

How to Reproduce

Uploading a test app with only the AppLovinSDK, and submitting it for review in the AppStore.

Additional Info

No response

thomasmso commented 1 month ago

Hey @x3mpablom - We're aware of the issue, it seems that Apple is not correcting picking up our SDK's privacy manifest. We'll notify this thread when we have an updated SDK.

x3mpablom commented 1 month ago

Hey @thomasmso Thanks for the quick reply! Do you know if this is an issue with the way the applovin sdk is providing the privacy manifest? Or is this an issue on Apple's side?

thomasmso commented 1 month ago

Seems to be related to how Apple is detectig it which no SDK provider would've been able to foresee.

thomasmso commented 1 month ago

Looks like Apple is only detecting the Privacy Manifest if it is bundled in a specific way in our SDK. We'll have to upload a new version of our SDK with the fix (1-2 weeks eta). I'll update this thread when the SDK is live.

fabneg commented 1 month ago

Hey @thomasmso ! I'm having the same issue but with a different sdk. Could you perhaps help by telling me how should the privacy manifest be bundled? Or point to a relevant documentation?

Thanks you very much!

thomasmso commented 1 month ago

Hi @fabneg - it would be quite hacky and several things could break in the process. Seeing that Apple is not rejecting builds in the meantime and only sending our warning emails, I would advise waiting for our next SDK release for a seamless integration experience.

fabneg commented 1 month ago

Hey @thomasmso! I think you misunderstood my question. I'm not currently using the AppLovin Sdk, or any Ads Sdk at all. But I have a similar issue with a different sdk, and so far I've not been able to find anything online, except for this thread. Would you kindly share how you are thinking of fixing this issue?

Thanks!

thomasmso commented 1 month ago

Hi @fabneg - at a high level, the Privacy Manifest file must be within the .framework directory of their SDK. But for direct support, you'll have to reach out to those teams.

christophercong commented 1 month ago

Hi @x3mpablom @fabneg,

Our latest SDK release, 12.4.0, addresses the issue of the privacy manifest detection by the AppStore Connect

x3mpablom commented 1 month ago

Thanks @christophercong! We'll try it out as soon as possible then.

x3mpablom commented 1 month ago

Hey @thomasmso @christophercong, I tried uploading a new version and the issue persists, the AppStore warning is still there. If it helps, we are integrating AppLovin via cocoapods.

thomasmso commented 1 month ago

@harryarakkal and I are looking into it.

thomasmso commented 1 month ago

@x3mpablom - This is due to inconsistency in Apple's detection method for privacy manifests. We'll be releasing a new SDK v12.4.1 later today which should address the issue.