Hello, We contacted Apple Developer Support due to an automatic message we receive when trying to publish a new version of our app The app links to non-public libraries in Frameworks/UnityFramework.framework/UnityFramework: /System/Library/PrivateFrameworks/AVFCore.framework/AVFCore. 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. The problem is we do not understand what the issue is even when reading your automatic message. How can we debug this ? How can we identify the source of the problem ? Do you have any idea of what the problem is ? What we tried : We tried to re-publish the application we currently have on your store (production) with different build number => App rejected with the same automatic message ; We tried to look fo
Search results for
ITMS-90158
1,686 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I have the similar situation on my mac-mini now (Feb, 2024, Sonoma 14.3.1). I have several records for testflight in my keychain. And old records work well. But a new record (I created it today) doesn't work. I have these messages: dmitriy@Mini-Dmitriy IPA % xcrun altool --upload-app --type ios --file app.ipa --username dmitriy@.com --password @keychain:TESTFLIGHT_PROD --verbose 2024-02-24 17:16:24.810 Starting altool... 2024-02-24 17:16:24.813 Initializing bundle from: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/Frameworks/AppStoreService.framework 2024-02-24 17:16:24.819 Will look for transporter at executable bundle relative path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2024-02-24 17:16:24.819 Looking for Transporter at path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2024-02-24 17:16:24.819 Looking for Tr
Topic:
Code Signing
SubTopic:
General
Tags:
I am having this exact same problem. I am totally blocked by this issue and I cannot release anything to testflight or Itunes connect.Furthermore, when I attempt to use the application loader, I continue to recieve error (this might be a separate issue) with validation errors for app icons that have been defined. All the assets are there, copied as part of the asset catalog.ERROR ITMS-90022: Missing required icon file. The bundle does not contain an app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format for iOS versions >= 10.0.ERROR ITMS-90023: Missing required icon file. The bundle does not contain an app icon for iPad of exactly '167x167' pixels, in .png format for iOS versions supporting iPad Pro.ERROR ITMS-90023: Missing required icon file. The bundle does not contain an app icon for iPad of exactly '152x152' pixels, in .png format for iOS versions >= 10.0.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
I received an email with the following message from Apple: ITMS-90725: SDK Version Issue - This app was built with the iOS 15.5 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. Well, what's the problem Apple? I used 15.5. That's later than 15!
Same here. Hope this gets resolved ASAP.For the record the way to do it with iTMS transporter is detailed here:https://stackoverflow.com/questions/30912572/itmstransporter-how-to-upload-content-in-in-app-purchase
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Hi Eveyone , Its not a webview error, you are using old api's ex- ( app share api or somethin like itms) you have change new url like (https).
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
Seeing this crash too. I believe it's been around since the first release of M1 Macs. Confirming also that workaround of using itms-apps://apple.com/app/id***** works.
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
I am still unable to upload to Testflight with an icon composer file as the main app icon on Beta 5. I continue to get: ITMS-90717: Invalid large app icon
Topic:
Developer Tools & Services
SubTopic:
Instruments
Tags:
Found the problem : I had mistakenly created the iTunes Connect app record under my own team YYYY, instead of team XXXX.For search purposes : the error number is ITMS-90159
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
plus itunes connect wants me to add a plist key:ERROR ITMS-90513: Missing Info.plist Key. Your app's Info.plist in 'Payload/AccuWeatherTV.app' must contain the 'TVTopShelfImage.TVTopShelfPrimaryImageWide' key.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Does anyone knows what to do in regards to ITMS-90339: This bundle is invalid - The Info.plist contains an invalid key 'UIApplicationExitsOnSuspend' in bundle OSU RadApp [OSU RadApp.app] this problem?Im having the same issue
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
Seeing the same as well:ERROR ITMS-90190: Invalid Info.plist Key. The key 'UIUserInterfaceStyle' in the Payload/APPNAMEHERE.appInfo.plist file is not valid.The issue has been observered through Archive and Fastlane upload.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
My app (com.onon.app) consistently fails App Store Connect validation (ITMS-90207: Invalid Bundle) despite passing all local diagnostics (valid arm64 binary, correctly signed, appropriate entitlements). Is there a known issue with Apple's validation server, or are there obscure validation rules I might be missing? Diagnosic info Architecture Check (lipo -info Runner): Non-fat file: Runner is architecture: arm64 Code Signing Verification (codesign -vvv Runner): Runner: valid on disk Runner: satisfies its Designated Requirement Local Environment Details: Operating System: macOS 15.5 24F74 (arm64) Xcode Version: 16.3 (16E140) Transporter Version: 1.3.3-13326 Flutter Version: 3.29.0 CocoaPods Version: 1.16.2 Has anyone encountered a similar issue with a Flutter app that passes local code signing checks but is rejected by App Store Connect? Are there any known edge cases or obscure validation rules that aren't covered by standard code signing diagnostics? I've also opened a Technical Support Incident with
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
I have been able to also reproduce the issue with a Xcode 15.3 template project after adding Apple Vision as a supported destination, configuring Xcode Cloud and adding a TestFlight post-action (without the post-action, the archives succeed). Submitted FB13774427 (Xcode Cloud visionOS archive action fails for iOS template project with Apple Vision added as supported destination.) as this might be a bug. Anybody successfully building these visionOS/iOS hybrid apps with current version Xcode Cloud after including a TestFlight post-action? The following email references ITMS error numbers: TMS-90508: Invalid Info.plist value - The value for the key 'DTPlatformName' in bundle DualUse.app is invalid. ITMS-90039: Type Mismatch - The value for the Info.plist key CFBundleIcons.CFBundlePrimaryIcon is not of the required type for that key. See the Information Property List Key Reference at https://developer.apple.com/library/ios/documentation/general/Reference/InfoPlistKeyReference/Introduction/Introd
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
I had the same problem, I found a solution in my case.Check here http://stackoverflow.com/questions/37493049/itms-90668-invalid-bundle-executable-the-executable-file-contains-incomplete/37513680#37513680
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags: