“ITMS-90338”

Now receiving the following warning in Xcode when uploading app, and corresponding email. The app is unlikely to be released for Vision Pro. Is there any flag I've missed that can be added to the app to silence this (blacklist the device type), bearing in mind this app is not compiled with the Xcode Beta that supports Vision Pro. Failing that, can anyone suggest who to reach out to at Apple to request a solution? I realise this is only a warning, but it's an unwanted distraction. Dear Developer, We identified one or more issues with a recent delivery for your app, Cape Physio 0.52 (7). Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90984: Apple Vision Pro support issue - The app contains the following UIRequiredDeviceCapabilities values, which aren’t supported on Apple Vision Pro. [accelerometer, gyroscope] After you’ve corrected the issues, you can upload a new binary to App Store Connect. Best regards, The App Store Team

Hello , I trying to upload app clips to app store but I get this error can anyone help me for find this solution and thanks: ERROR ITMS-90823: Invalid entitlement. Bundle '*********' cannot use the 'com.apple.developer.on-demand-install-capable' entitlement. Remove the 'com.apple.developer.on-demand-install-capable' entitlement.

No Proxy for Xcode 15: _with Xcode 14 You can modify this file : /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/java/conf/net.properties and set the following property to true ( false by default ) java.net.useSystemProxies=true_ With Xcode 15, I don't found any solution **Utilisation of environment variables http_proxy and https_proxy it's useless because it's ignored #** how I can define a proxy in order to sign with Xcode command lines ?

When I send a build in Xcode the process occurs normally, but a few minutes later I receive an e-mail saying: ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “xxx.app” bundle should contain a NSMicrophoneUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. So the problem is the description of the use of the microphone, right? As the attached image shows that I have already done this process, and I continue to receive this error. Even when I remove the part of the avfoundation code that uses the microphone to try to submit the build, the error continues to be returned to me

Hey! Since thursday we are have problem that we can not submit new builds on app store. This is the error we are getting: ITMS-90338: Non-public API usage - The app references non-public selectors in Frameworks/UnityFramework.framework/UnityFramework: initWithImageData:. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ App validates fine in xcode before uploading, but after uploading we get this error, any suggestions what to do?

After adding PrivacyInfo.xcprivacy following this Steps: https://vikramios.medium.com/itms-91053-missing-api-declaration-3c2bef935bd3 I am getting this error ❌ error: Multiple commands produce 'app_dir/PrivacyInfo.xcprivacy';

In order to facilitate management, we integrate some SDKs such as Firebase into one of our own internally used SDKs. Recently, when submitted to the appstore, we were prompted that FirebaseCrashing included in the SDK lacked the necessary signature (ITMS-91065). The information that can be confirmed is that after packaging the SDK through secondary packaging, the original signature is lost. And we have a static reference. So what I want to ask is whether we can only manually sign our secondary packaging sdk (the signature is our own certificate different from the original Firebase) to solve this ITMS-91065 problem. According to the description of the Apple Developer Conference, Apple only verifies the consistency and security of the SDK and does not record the signature of each SDK on Apple's servers. Therefore, you should only need to ensure that the SDK is in a signed state to comply with Apple's review requirements. (My guess is still being verified)

While I'm keen on being on the latest version of macOS, I'm having trouble meeting the requirement that my app can run on a version of macOS that doesn't exist :) I'm using Xcode 15.2 (15C500b), targeting iOS 17.2. I've elected to have the App Store choose the minimum version for Catalyst. I've also tried selecting a version. ITMS-90899: Apple silicon Mac support issue - The app is not compatible with the provided minimum macOS version of 14.2. It can run on macOS 14.4 or later. Please specify an LSMinimumSystemVersion value of 14.4 or later in a new build, or select a compatible version in App Store Connect. For details, visit: ... Is there something I could be doing wrong to prompt this behaviour?

One of our apps got hit by the ITMS-91065: Missing Signature issue when we attempted to distribute it to externally via TestFlight. The email said FirebaseCore is missing the signature file within our own framework. After investigation, I realized our recent update to the version of Firebase that has the proper signatures and privacy manifest wasn't enough by itself. Similar to Apple's own instructions on embedding static frameworks since Xcode 15, Firebase instructs us to select the Embed & Sign option. After making the appropriate changes though, we're getting the error in Transporter: Asset validation failed (90085): No architectures in the binary Our setup is as follows: We have an analytics dynamic framework, which depends on Firebase's static framework. The Firebase related frameworks are embedded and signed in our analytics framework. Our app depends on the analytics dynamic framework, which now includes Firebase frameworks within its framework. Since the Firebase frameworks are static, on

I've complied with the reason declaration following the links sent by the autogenerated emails for the surface level Runner declaration, however libswift has the incorrect values for the reason codes for UserDefaults. I've checked their github and there is no way to add issues since it is read-only. I'm also in the dark for who to contact regarding this. Does anyone have any idea how to resolve this aside from manually changing the privacy files? I don't want to have to do this each time I do pod install. ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/libswiftObjectiveC.dylib” file contains “DDA9.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryUserDefaults category.

Apple send a mail when I publish my ipa. Please correct the following issues, then upload again. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “app-alt-icon-mountain” that references asset “山青.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “app-alt-icon-fantasy” that references asset “梦幻.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “app-alt-icon-bubble” that references asset “泡泡.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFBundleAlternateIcons contains an entry “app-alt-icon-night” that references asset “暗夜.” No such asset is present in the asset catalog. ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons~ipad.CFB

Hi, our app has been using single size app icon for a while and today when I trying to upload a new version of our app I got an email from App Store Connect saying ITMS-90013: Corrupt Image File - The image file 'AppIcon60x60@2x.png' appears to be corrupt. We haven't touched the image for ages and these 60x60 image were generated by Xcode from the single 1024x1024 image supplied. I've tried to use a new image and still got the same error. Does anyone experienced this recently?