ITMS-90338

1,571 results found

Post

Replies

Boosts

Views

Activity

ITMS-90382: Upload limit reached
We've started hitting this limitation when submitting builds using Xcode Cloud. ITMS-90382: Upload limit reached - The upload limit for your application has been reached. Please wait 1 day and try again. We generate TestFlight builds for every PR (builds from PR get sent to QA & devs) & for every merge (builds get sent to everybody in the team). Is there any way to know what's the limit so we can try to work around it? Edit: I've just checked, and TestFlight only reports 19 builds that are expiring in 90 days (aka were uploaded within the last 24h). Is the limit that low?
3
0
2.2k
Mar ’23
Reply to TestFlight build upload with error ITMS-90338: Non-public API usage
Same issue here ITMS-90338: Non-public API usage - The app references non-public symbols in Contents/MacOS/ Flagged symbols: _AVCaptureDeviceSubjectAreaDidChangeNotification, _AVCaptureDeviceTypeBuiltInDualCamera, _AVCaptureDeviceTypeBuiltInDualWideCamera, _AVCaptureDeviceTypeBuiltInTelephotoCamera, _AVCaptureDeviceTypeBuiltInTripleCamera, _AVCaptureDeviceTypeBuiltInUltraWideCamera, _AVCaptureSessionPresetInputPriority
Jun ’24
TestFlight build upload with error ITMS-90338: Non-public API usage
Hello, today when we uploaded a new TestFlight Mac Catalyst build we received an email about the build being invalid: TMS-90338: Non-public API usage - The app references non-public symbols in {app name}: _AVCaptureDeviceTypeBuiltInTelephotoCamera, _AVCaptureDeviceTypeBuiltInTrueDepthCamera, _AVCaptureDeviceTypeBuiltInUltraWideCamera, _AVCaptureSessionInterruptionReasonKey, _AVCaptureSessionInterruptionSystemPressureStateKey, _AVCaptureSystemPressureLevelCritical, _AVCaptureSystemPressureLevelFair, _AVCaptureSystemPressureLevelNominal, _AVCaptureSystemPressureLevelSerious, _AVCaptureSystemPressureLevelShutdown. 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 htt
2
0
603
Jun ’24
What can trigger "App uses the itms-services URL scheme to install an app" rejection?
I'm an indie developer. My latest minor update for my game which has been on the Mac App Store for 13 years and which has spent time at #1 on the download charts just started getting rejected for the following reason: Guideline 2.5.2 - Performance - Software Requirements The app installed or launched executable code. Specifically, the app uses the itms-services URL scheme to install an app. However my app is certainly not installing any apps and to the best of my knowlege it is not using any itms/itunes/etc. type URLs in any way, so I can't figure out what would be triggering this claim. Inquiries as to what app I am supposedly installing or what URL I am supposedly using have yielded 'no further information can be provided'. Has anyone run into something similar? Any ideas on obscure scenarios that could trigger this particular rejection? Or any advice on what one should do in my situation? I feel a bit stuck. Has anyone had luck with the appeal process for this sort of thing (to at least g
2
0
813
May ’24
ITMS-90809: Deprecated API Usage
Our app submission is being rejected with the following error message: TMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. We have thoroughly scanned our code and all dependent libraries for references to UIWebView and found none. looking for help, on how to address this issue
5
0
548
Jun ’24
Reply to Transporter 1.3 Error
Although I had accepted the answer from the App Store Connect Engineer (as it does get around the error in Transporter 1.3), it presented a new problem after uploading the app. Without the LSMinimumSystemVersion key in the Info.plist, I get an email from App Store Connect with the following issue: ITMS-90899: Macs with Apple silicon support issue - The app isn‘t compatible with the provided minimum macOS version of 11.5. It can run on macOS 12.0 or later. Please specify an LSMinimumSystemVersion value of 12.0 or later in a new build, or select a compatible version in App Store Connect. For details, visit: https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/manage-availability-of-iphone-and-ipad-apps-on-macs-with-apple-silicon. The app minimum deployment is iOS 14.7. I tried setting the macOS minimum version for the app via the instructions (on App Store Connect - Pricing and Availability page) but I still get the issue email. This happens if I set it to Automatic (11.5) o
Jun ’24
ITMS-90111: Invalid Toolchain
Hi,I updated to 10.15beta and started getting this error:ITMS-90111: Invalid Toolchain - Your app was built with a beta version of Xcode or SDK. Apps submitted to the App Store must be built with the GM version of Xcode 9 and the SDK for iOS 11, tvOS 11, watchOS 4, or macOS 10.13 or later.My Xcode is still GM (10.2.1) so not sure what this error is trying to tell me, since I've been always keeping Xcode to stable version and MacOS on latest beta.Has anyone expriencing the same problem or have a solution to my issue ?Thanks.
16
0
9.3k
Jun ’19
xCode - ITMS-90111: Unsupported SDK or Xcode version
When I try to upload an app to the AppStore, I receive following feedback: I had Xcode 16 with visionOS installed. Because of the feedback, I switched back to Xcode 15.3 with visionOs 1.0. I archived it again and tried to upload the app again. But I still receive the same feedback. I also tried https://stackoverflow.com/questions/56518791/app-store-refuses-my-update-after-installing-xcode-11-beta-with-keeping-xcode-10/56623421#56623421, but it seems that there is no such property for visionOS in the info.plist I do not have any further ideas...
2
0
818
Jun ’24
Vision Pro + Device Capabilities warning, how to silence?
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
4
0
5.5k
Sep ’23
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."
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.
2
0
777
Nov ’20
Reply to 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."
我的app在交付过程中保如下错误,搜代码 并未找到该方面的引用,想咨询下如何解决 ,谢谢 ERROR ITMS-90823: Invalid entitlement. Bundle 'HBuilder.app' cannot use the 'com.apple.developer.on-demand-install-capable' entitlement. Remove the 'com.apple.developer.on-demand-install-capable' entitlement.  ERROR ITMS-90918: Missing Info.plist value. The “HBuilder.app” bundle has the com.apple.developer.push-to-talk entitlement, but the required UIBackgroundModes Info.plist key value, push-to-talk, is not included.  ERROR ITMS-90926: Invalid entitlement. The “HBuilder.app” bundle has the com.apple.developer.media-device-discovery-extension entitlement, but only Media Device Discovery extensions should have this entitlement. Please remove the com.apple.developer.media-device-discovery-extension entitlement and upload a new build.
Jun ’24
Impossible to define Proxy on Xcode 15
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 ?
1
0
371
Jun ’24
Reply to What can trigger "App uses the itms-services URL scheme to install an app" rejection?
Hi, Unfortunately I have no solutions to offer but I just wanted to add a comment that I'm facing the same issue with my application. I'm not using itms-services URL at all and am certainly not intentionally trying to install another app. I have a previous version approved on Testflight but can't get my latest version approved due to this issue. When I replied to the App Review, I received the same reply of 'no further information can be provided' so I don't really know what else I am to do. It's a really frustrating experience to have your app rejected and then when you try to resolve the issue, getting told we can't tell you where you did this, but we definitely saw it somewhere.
Jun ’24
Invalid binary when submitting a build to appstore connect
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 “***.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
1
0
444
Jun ’24