Apple began sending emails on March 13, 2024. Submission to launch the app Submission to use external TestFlight In my experience, if there is a PrivacyManifest problem in the above situation, an e-mail was sent within 5 minutes. (You can see that you will receive an e-mail almost at the same time as you submit it.) The best way is to submit it to an external TestFlight while changing the build.

I'm just wondering. Was there anything about BLE in 'Privacy Manifest'??

@DTS Engineer If I test it Even if I set up "Mach-O type build settings for static libraries" If I don't set the 'Embed' option in my app, I won't recognize Privacy Manifest.

Did you add PrivacyInfo to the app?? Is the API of the SDK that you didn't write the same as the API that you used in the app?? Is the commonly used SDK in the list using the Required Reason API??

@eskimo Thank you for your response. We are making navigation apps and there are two projects. Both have engine part, one c based, the other c++ based. We don't know if c or c++ has something to do with this error, but only c++ project makes this errors. They are iPhone/iPad apps, and yes, they are XCode projects. Since it's a big project, we didn't try making a new project yet.

Apple says you need to add it to both the app and the library. But I think there must be a situation where that's not possible. I tested it. Even if you don't add PrivacyManifest from the library, adding content to PrivacyManifest in the app will fix the problem.

SwiftyJSON has fixed this issue. Check out the latest updates. If there are more libraries that have been interrupted, you should check. 1. Verify that the library requires PrivacyManifest. you submit the app where the library was used to TestFlight for verification. Apple will send you an email if you have any issues. If you don't have an app, check out the library yourself. 2. If you don't have anything to write about, you don't need PrivacyManifest. 3. If you need to fill out something in the Library PrivacyInfo, choose from the following methods. Keep in touch with your library developer for updates. Fork the library to add PrivacyInfo. In the app's PrivacyInfo, type the type that the library has. I think the third method would be the simplest.

@jumping_frog Same here, I'm having issues after the update. I have a problem with iOS 17.5.1. I think this is a bug.