Provide Privacy Manifest support for AFNetworking about alamofire HOT 35 CLOSED

I tried yesterday to upload a TestFlight build containing privacy changes for my app, and I was using AFNetworking since very long time. This time I did not get any warning for privacy APIs.

Also, confirmed by @jshier that AFNetworking doesn't use any privacy APIs & myself also confirmed just searching code.

from alamofire.

You'd have to ask Apple. If you link AFNetworking statically, the linked targets manifest will cover it anyway.

from alamofire.

wlxo0401 you can fork it in your personal repo

from alamofire.

Hmm so what could be the point of having it? Even Apple suggests to avoid adding empty Privacy Manifests if SDK does not require it.

https://forums.developer.apple.com/forums/thread/746481

Thanks @jshier
Just seeking clarity on the web as one of our project continues to utilize AFNetworking, and we're actively collecting essential details to align with upcoming guidelines.

from alamofire.

@mithleshgomotive

Create a simple project that is empty and add AFNetworking.

And submit the test flight external distribution.

If you have a problem, you can receive the mail content and add Privacy Manifest.

If you don't have a problem, you can add an empty Privacy Manifest.

However, Apple is recommending that Privacy Manifest be removed if it is empty.

from alamofire.

You'll need to update whatever SDK you're using to directly integrate AFNetworking rather than using it as a framework. If you can link it statically, Apple's tools don't seem to detect it.

from alamofire.

@mithleshgomotive AFNetworking SDK is already in the project but Project is Whitelabeled APP. So, I submitted New Application on store and received mail and app is rejected.

from alamofire.

@jenhausu hi man is it possible for you to share the privacy manifest file ?

from alamofire.

+1 for privacymanifest and code signing requirements for AFNetworking

from alamofire.

@mithleshgomotive so according to apple it means if we include any listed SDK and then send the update to app store connect or we create a brand new app with listed SDKs and submitting it to apple, only in those two scenarios we need to include manifest file for those SDKs?
But if our app is 6-7 years old already using AFNetworking, and already on the app store, so after 1 May 2024, if we do not include a manifest file in that for the listed SDK, then Apple can reject our app.?

from alamofire.

Got this response from Apple when submitted App.

TMS-91065: Missing signature - Your app includes “Frameworks/AFNetworking.framework/AFNetworking”, which includes AFNetworking, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. If a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a signature file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a signature. For details about verifying the code signature for a third-party SDK, visit: https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks.

from alamofire.

Hey guys, I've been playing around the privacy manifest recently, I think AFNetworking doesn't use any of the listed APIs, so it actually doesn't need to add the privacy manifest.

from alamofire.

AFNetworking will not be receiving any update. It hasn't been updated in four years and I deprecated it a year ago. Apple obviously didn't look at the state of the project when it was added to any lists. As recommended when it was deprecated, either upgrade to Alamofire or copy AFNetworking into your project.

from alamofire.

@jshier
Does copying AFNetworking networking to the project mean using the code as a direct declaration to the project rather than installing it in the form of a library???

from alamofire.

@mohsinbmwm3 I know AFNetworking is in Apple's list but does it use any of the listed APIs?

from alamofire.

I don't believe so.

from alamofire.

AFNetworking is being used by so many people that it would be nice to add a private list to make it easier for all developers. I hope the author can see it.

from alamofire.

If there are any types you need to add, add them to PrivacyInfo on the app.

from alamofire.

Even in my project, AFNetworking is being used, and not sure what to do, should upgrade to Alamofire, or is there another way?
Could someone please let me know...

from alamofire.

@abhistin Upgrading to Alamofire takes a lot of effort, so I fork AFNetworking to my organization and add privacy manifest myself.

from alamofire.

@jenhausu can you share privacy manifest file here - what all APIs it has ?

from alamofire.

@jenhausu Yes please if you could share the privacy manifest for AFNetworking, otherwise I think I need to dig into its code.

from alamofire.

Hi I just saw Sean Allen video on privacy manifest and got a doubt at this timestamp https://youtu.be/T6IvImk66m8?si=SY8iapTOIDs-J-j1&t=153
If I have an app 6-7 years old using AFNetworking, then the rule(to include manifest file for AFNetworking) doesn't apply to my app?
Is it for If I include the AFNetworking library now in my project and if I am creating a brand new app with AFNetworking?

Could any body please give me a confirmation on it.

from alamofire.

@abhistin this is as per Apple.

Starting in spring 2024, you must include the privacy manifest for any SDK listed below when you submit new apps in App Store Connect that include those SDKs, or when you submit an app update that adds one of the listed SDKs as part of the update.

from alamofire.

@abhistin In the youtube video of Sean Allen he mentioned in comments that older apps also have to do this even the older app haven't added any SDK

from alamofire.

I'm trying to figure out that do I have to work on this or not as we are not getting any warning emails. We released an update today but no warning mails are coming for privacy manifest.

from alamofire.

I'm trying to figure out that do I have to work on this or not as we are not getting any warning emails. We released an update today but no warning mails are coming for privacy manifest.

Same here. We also use AFNetworking and haven't received so far any warning. We're a bit confused :)

from alamofire.

Are you submitting a new app or adding AFNetworking in an update? If not, that warning seems spurious, but I'll reach out to Apple again. AFNetworking will not be receiving an update.

from alamofire.

@jshier Submitted new application. And Not able update SDK in project due to project limitation.

from alamofire.

@bhargavbajani-simformsolutions - did you mean here - You have added this AFNetworking SDK in your app's project for the first time now or it was already added ?

from alamofire.

In that case it sounds like you can just integrate AFNetworking directly into the app rather than using it as an external framework. In that case it shouldn't be an issue to ASC.

from alamofire.

@jshier Yes I'll try with that. Thanks for your quick responses.

from alamofire.

In that case it sounds like you can just integrate AFNetworking directly into the app rather than using it as an external framework. In that case it shouldn't be an issue to ASC.

Is it ok if I use CocoaPods to integrate AFNetworking, and don't use use_framework!? For this will not produce .framework file to the app bundle.

from alamofire.

bundle

I guess Yes, as I have same setup and I didn't get any warning from apple for AFNetworking

from alamofire.

No response :(

from alamofire.