ITMS-90338

I just submitted a build to TestFlight this morning that should have set off the same alarms as last week, but it didn't. We received no emails complaining about ITMS-91053 violations like happened on this branch before. We've been working hard to figure out how to meet your new privacy requirements, and it's been quite frustrating. I thought I finally fixed it yesterday, but today I wanted to run a sanity test. I went back and created a build that should fail, but now that one is apparently fine as well. I'm at a complete loss.

Hello, I'm create an app using QT on MacOs with Generate to Xcode, when submitting it to the App Store the upload process was successful but I got email feedback with the message containing the following: ITMS-90238: Invalid Signature - The main app bundle Tren at path Tren.app has following signing error(s): a sealed resource is missing or invalid . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple .com/library/mac/technotes/tn2206/_index.html for more information. ITMS-90296: App sandbox not enabled - The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[Tren.app/Contents/MacOS/Tren ]] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app.

Morning All, just wanted a little help with my xamarin forms app. When I publish to test flight for a public test build I am always receiving the email about ITMS-91053: Missing API declaration. I have followed the steps and created a PrivacyInfo.xcprivacy in Xcode and I can see it in my xamarin iOS project but I still get the email saying it is missing. Is there something I am missing or ned to reference in the info.plist etc. My looks like the following: `

Since yesterday (03/22/24) we are unable to upload new or existing builds to AppStoreConnect. We get the following error - “Error ITMS-90432 Unexpected file found in Frameworks. MyApp.app/Frameworks/Configurations” file is in the Frameworks directory, but the Swift runtime libraries are the only files permitted in that directory. Please remove this file and upload a new build. (ID: 57e219ea-d27e-465d-9e9b-ec41d3a0b1f7). We have tried rebuilding targerts with no changes for Builds that use to upload ok and they now get the same error too. Is this an appstoreconnect bug? If not where is the Frameworks directory and how do we remove the file?

Hello, I have a question regarding the Privacy Manifest of a third-party SDK. We are using a static third-party SDK. This third-party SDK use the UserDefaults API, and it is also specified in the Privacy Accessed API Types within PrivacyInfo.xcprivacy. The static third-party SDK is added as a dependency via CocoaPods, and PrivacyInfo.xcprivacy is included in the Pods Resource. Additionally, our app does not use UserDefaults API. When we generate the Privacy Report, it correctly shows the data collected by the third-party SDK. However, when we submitted for review, we received a warning email stating that UserDefaults is being used in the app but is missing from the Privacy Manifest. ITMS-91053: Missing API declaration - Your app’s code in the “MyApp” 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 inc

We are getting warnings from Apple, ITMS-91053 Missing API declaration, for categories Disk Space, Timestamp, and more. But we've checked our source code to make sure we are not making any of the entry points at issue. We suspect they are being called from one of the 3rd party frameworks we use, some of them are binary xcframeworks. Is Apple planning on extending their warnings to provide more information about where the usages are? Are we left to find it ourselves? Do we need to resort to adding those reasons to our app's manifest? Which seems hacking since we probably don't know when of the allowed reasons are accurate.

I am having trouble submitting the next build of my macOS app to the App Store Connect. I keep getting a variation of this error: ITMS-90238: Invalid Signature - The main app bundle MyApp at path MyApp.app has following signing error(s): code has no resources but signature indicates they must be present In subcomponent: MyApp.app/Contents/Frameworks/GoogleAppMeasurement.framework . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information. ITMS-90238: Invalid Signature - The main app bundle MyApp at path MyApp.app has following signing error(s): code has no resources but signature indicates they must be present In subcomponent: MyApp.app/Contents/Frameworks/GoogleAppMeasurementIdentitySupport.framework . Refer to the Code Signing and Application Sandboxing Guide

Hi guys, need some help on this issue when I submit my testing app to TestFlight using GitHub Actions and Fastlane, I get this warning from App Store Connect: We noticed one or more issues with a recent delivery for the following app: Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-90725: SDK version issue - This app was built with the iOS 16.2 SDK. Starting April 29, 2024, all iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution. I am using React Native CLI, and Fastlane to run and build my app through Github Actions. After scouring around, from what I understood was that all I needed to do was just to update my Xcode and iOS SDK to the latest, which I did. Currently my Xcode is 15.2 and iOS SDK is on 17 already. However, I still receive this warning w

This is the mail I received from Apple while testing. If you look at it, it shows that there are two items that are problematic. As you can see, ITMS-91053: Missing API decimation shows the same problem in both, but the colors are displayed differently. (Purple, Gray) There were four problems in the mail I received while testing more, but all of them received the same color. Is this just a mail error?? Or does the color have a meaning?

I am trying to upload a new build of my app from the new Xcode 14.1 RC but it keeps failing with the below error: ITMS-90428: Invalid Swift Support - The files libswift_Concurrency.dylib don’t match /Payload/MY_APP.app/MY_APP_WatchOS.app/libswift_Concurrency.dylib. Make sure the files are correct, rebuild your app, and resubmit it. Don’t apply post-processing to /Payload/MY_APP.app/MY_APP_WatchOS.app/libswift_Concurrency.dylib. My bundle contains a watchOS 4.3 app which I thought might have been an issue, so I tried increasing it to watchOS 7.0 but still got the error. Bitcode is disabled for all targets. I don't have post-processing enabled either.

When I submitted to the MacOS Apple Store, it was rejected, and the following error was prompted, what should I do (I used a third-party build and signature, and did not use XCode) Dear Developer,We identified one or more issues with a recent delivery for your app, CollDesk 1.0.0 (1.0.0). Please correct the following issues, then upload again.ITMS-90332: Invalid Symbolic Link - The symbolic link 'com.colltech.desk.pkg/Payload/CollDesk.app/Contents/Frameworks/QtPrintSupport.framework/Headers' resolves to an invalid location. Make sure that the symbolic link does not resolve to itself, and that the location exists and is contained within the app bundle.ITMS-90332: Invalid Symbolic Link - The symbolic link 'com.colltech.desk.pkg/Payload/CollDesk.app/Contents/Frameworks/QtGui.framework/Headers' resolves to an invalid location. Make sure that the symbolic link does not resolve to itself, and that the location exists and is contained within the app bundle.ITMS-90332: Invalid Symbolic Link - The symbolic link 'com.c