Missing privacy manifest - 2

App Inventor for iOS
1

Hello!
I uploaded the application to the App store connect today and a few minutes after receiving the status "Waiting for review", the application was rejected with the message:

Please correct the following issues and upload a new binary to App Store Connect.
*ITMS-91061 Missing privacy manifest - Your app includes “Frameworks/Alamofire.framework/Alamofire”, which includes Alamofire, an SDK that was identified in the documentation as a commonly *
*used third-party SDK. If a new app includes a commonly used third-party SDK, or an app update adds a new commonly used third-party SDK, the SDK must include a privacy manifest file. *
*Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs *
that are required to include signatures and manifests, visit: Third-party SDK requirements - Support - Apple Developer

This rule forced on February 12, 2025 as they warned. Who knows the solution, share please.

1 Like
2

Yes we are aware of the new policies. Unfortunately, I have not had time to update our build system to be compatible with the new Apple requirements. I will see about getting to by the end of next week.

2 Likes
3

Understood, thank you!

4

How do we find out?

I have the same problem.

5

Hi?

6

I'm working on it. I'll report back when the server is updated.

2 Likes
7

Hi, any news?

1 Like
8

I am working on fixing a few things after merging with the latest version of App Inventor. It should be going out tomorrow barring any other issues.

3 Likes
9

The build server has been updated to include a default privacy manifest in the app that matches what we use in the MIT App Inventor companion. New project builds should pick this up automatically.

3 Likes
10

Sorry, the same result: The status of your app has changed to Invalid Binary.

Please correct the following issues and upload a new binary to App Store Connect.

ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/Alamofire.framework/Alamofire”, which includes Alamofire, an SDK that was identified in the documentation as a commonly used third-party SDK...

11

Hello,
The IPAs files are not running. We can compile the ios AIA but for exec it close without any message. May be we need a new certificate or provisioning file.

1 Like
12

Yes, I also tried to update my app and got the same type of error.

1 Like
13

hi? any solution? i need update my app. Please.

1 Like
14

I've pushed an update to the buildserver that should fix the crash on start.

1 Like
15

Please correct the following issues and upload a new binary to App Store Connect.

ITMS-91061: Missing privacy manifest** - Your app includes “Frameworks/Alamofire.framework/Alamofire”, which includes Alamofire, an SDK that was identified in the documentation as a commonly used third-party SDK. If a new app includes a commonly used third-party SDK, or an app update adds a new commonly used third-party SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: Third-party SDK requirements - Support - Apple Developer.

Apple Developer Relations

16

I am not getting this error when I upload my test apps to the App Store. Did you bump the version number in your project settings? Otherwise, it might be that App Store Connect is referencing an old build with the same version number.

17

I did bump the version number in my project settings before uploading the new build. As you know, the App Store does not accept a new submission without a version increment.

Despite this, I am still encountering the ITMS-91061: Missing Privacy Manifest error. My app includes Alamofire, which seems to be triggering this requirement. Could you please confirm if the latest version of Alamofire includes the required PrivacyInfo.xcprivacy file? If not, should I manually add it.

18

It should be added automatically during the build. For example, I just exported using the Ad Hoc option and opened the IPA file and it is in there.

@Ferran_SIMON Are you also encountering this issue? I know you push to the App Store fairly regularly.

1 Like
19

I had only test with the IPA. Since the IPA failed, I have not tried uploading to the Apple Store. My issue is in the IPA built before upload it to the Apple Store.

1 Like
20

I uploaded the application to the App Store by changing the first digit of the version (from 1.7.7 to 2.0) just now. Literally after a couple of minutes I received the same error "Missing privacy..".
I use "Upload to iOS App Store". The new version of app processed, there is not error. Error message and the corresponding letter appears only after submitting - "Add for review".
I described these details, since until February 12 a message about "unresolved issue" appeared immediately after the app' processing.

1 Like