Apple Privacy Manifest about alamofireimage HOT 10 CLOSED

+1

from alamofireimage.

Alamofire is specifically listed as needing a privacy manifest: https://developer.apple.com/support/third-party-SDK-requirements/

from alamofireimage.

Alamofire has an open PR to add one, pending more confirmation from Apple about what exactly is needed. Alamofire/Alamofire#3792 AlamofireImage doesn't use any of the limited APIs and so shouldn't need one at all.

from alamofireimage.

@jshier Do you have confirmation from Apple that Alamofirelmage will not require this Manifest and will not include it? If so, I will cross this dependency off my list.

Thanks

from alamofireimage.

Since the PR is now merged will we have a release soon? 🙏

from alamofireimage.

If the SDK does not share user tracking details, does this actually require the update? We will update to the latest version regardless, but I'm interested in your insight here.

Thanks

from alamofireimage.

AlamofireImage shouldn't need its own manifest, as it doesn't use any of the newly restricted APIs (no Alamofire framework collects data of any sort). It should just inherit Alamofire's privacy policy automatically without update.

from alamofireimage.

@jshier Excellent thank you for the fast reply. I will mark this SDK down as it's not required to include the manifest! Great news there.

from alamofireimage.

Alamofire's privacy manifest shipped with 5.9.0, make sure to update.

from alamofireimage.

My reasoning is that if Alamofire is included in the list of privacy manifest requiring SDK's and AlamofireImage is depending on Alamofire then Alamofire needs to include the privacy manifest and AlamofireImage needs to point to that updated version as well.

Now I guess it depends on how deep into child's dependencies the Apple scanning goes 😅

from alamofireimage.