Search results for

ITMS-90158

1,685 results found

Post

Replies

Boosts

Views

Activity

Reply to TMS-90714: Invalid binary - The app contains one or more corrupted binaries
@AkhileshNak, your bug report is on its way back to you soon with this information, but I'm sharing what we found here for the community's benefit in the future. An app receiving this ITMS error can have Objective-C entries with empty names in the Objective-C metadata. To identify the binaries with those conditions, you can run the following Terminal command on each binary inside the app: % xcrun dyld_info -objc Payload/YourApp.app/YourApp | grep (null) Once you have that output, you can begin to work backwards based on the various class and method names to identify where in your project these are defined. If these are coming from a third-party library you're integrating in your app, you'll then need to talk to the vendor. — Ed Ford,  DTS Engineer
Jul ’25
Reply to ITMS-90207: Invalid Bundle. The bundle at 'Runner.app' does not contain a bundle executable.
Sharing the full email I sent to Apple Support I am consistently encountering the ITMS-90207 error Invalid Bundle. The bundle at 'Runner.app' does not contain a bundle executable. when attempting to upload my Flutter iOS app to App Store Connect via both Transporter and direct upload from Xcode Organizer. This issue persists despite extensive troubleshooting and thorough local validation, which shows the IPA is correctly formed. App Details: App Name: OnOn App Store Connect App ID: 6502598657 Bundle Identifier: com.onon.app Latest Version/Build Attempted: Version 1.0.24, Build 50 Error Details: Exact Error Message: Invalid Bundle. The bundle at 'Runner.app' does not contain a bundle executable. (ID: [e.g., f548c384-73e9-4f09-96a0-363b7d67f650 from your log]) Transporter Log Reference: From my Transporter logs, the specific iris-code is STATE_ERROR.VALIDATION_ERROR. Example Build ID from Transporter Log: [e.g., 6bd99937-1283-486e-a245-419ea29443f0] (This ID might vary with each attempt, but providing
Jul ’25
Strange warning after transporting app
Hi guys, I have an app ready for testing/distribution. But when I used Transporter to send the app to Apple Store Connect, I got the following warning. ITMS-90885: 'Cannot be used with TestFlight because the executable “${executable}” in bundle “${bundle}” is missing a provisioning profile but has an application identifier in its signature. Nested executables are expected to have provisioning profiles with application identifiers matching the identifier in the signature in order to be eligible for TestFlight.' The executable and bundle values were missing from this warning message, which does not help find the warning cause. Could someone give me some advice to resolve this issue? Thanks!
2
0
151
Jul ’25
ITMS-90338: Non-public API usage
I am using multi-targeted react native app i have deployed most of then but i didi''t get any error but one of my app greeted validated successfully and uploaded successfully but i got error message from play store that's is given below , ITMS-90338: Non-public API usage - The app references non-public selectors in ETCiso: _isKeyDown, _modifiedInput, _modifierFlags. 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 every setting are same as other, If there any error and issue in binaory then why its geeting approved in validation and geeted upload
1
0
100
Jul ’25
Icon Composer: Unable to Submit App to App Store Connect After Adding iOS 26 App Icon
Hello, I added a new iOS 26 app icon created with Icon Composer (named AppIcon) to my app, while keeping the previous version's icon (in Asset Catalog format, also named AppIcon). However, I found that once the bundle contains the Icon Composer icon file, the app cannot be submitted to App Store Connect. I received the following App Store Connect errors: 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. To support older versions of iOS, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/user_interface. 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. To support older oper
1
0
302
Jul ’25
Invalid Characters in Info.plist File
ITMS-90328: Your package contains a file AppName.app/Info.plist /Users/admin with a name that contains invalid characters. Avoid using control characters in the file names. ITMS-90328: Your package contains a file AppName.app/Info.plist with a name that contains invalid characters. How do I resolve this issue? My Info.plist file has no control character
4
0
200
Jul ’25
ITMS-90755: Invalid Binary
After uploading a debug build to testflight getting an email stating ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: AppName.app/App. Remove the instructions from the binaries, rebuild and resubmit.. To the best of our knowledge we haven't added any prohibited instructions of any kind, and the email also doesn't provide any information on what the offending instruction is. After much trial and error we found switching a property from an array to a non-array makes the error go away and testflight accepts the build, which obviously doesn't make any sense as to why that change produces this error. Is this some kind of false positive happening or what else is going wrong? Any help to resolving the issue is much appreciated.
1
0
637
May ’23
ITMS-90755: Invalid Binary
Hi, Recently our App is facing a generic error with no error details. This error is happening once Build has been successfully uploaded to AppStore Connect through Xcode Organiser. Steps followed while uploading the build: Archive the Build through Xcode Once Archive is successful, Distributing the App through Xcode Organiser using AppStore Connect distribution method. Build Uploaded successfully to AppStore Connect After 5 min we are receiving a email with below message Hello, We noticed one or more issues with a recent delivery for the following app: AppName App Apple ID 2121111 Version 3.6.9 Build 75 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: AppName.app/AppName. Remove the instructions from the binaries, rebuild and resubmit. Apple Developer Relations Solutions tried till now Updating Xcode to latest version of 16.4 Recreating new Distribution certificates and P
2
0
370
Jul ’25
Reply to ITMS-90755: Invalid Binary
DTS has seen this ITMS-90755 error before and our general advice is: Check your project for build settings that enable non-standard instructions [1]. If that doesn’t turn up anything relevant, the next step is to file a bug. However, I have some very specific advice in this front. I believe that you’re currently submitting your app to App Store Connect using the Xcode organiser window. That’s fine in general, but for this task I’m gonna suggest a tweak: In Xcode organiser, select the problematic Xcode archive. Click Distribute App and follow the Custom > App Store Connect > Export workflow. In that workflow, select the same signing options you normally select. That’ll export an archive, either a .ipa for iOS and friends or a .pkg for macOS. Find that archive. Use the Transporter app to upload that archive to App Store Connect. That should reproduce the problem; if it doesn’t, lemme know and I can zen on this some more. Assuming it does, file your bug with the details of the issue and attach the
Jul ’25
Reply to Invalid Characters in Info.plist File
ITMS-90328: Your package contains a file AppName.app/Info.plist /Users/admin with a name that contains invalid characters. Avoid using control characters in the file names. Is this the verbatim message? It looks like there is a file named AppName.app/Info.plist /Users/admin, where you should look how the file became named with that trailing /Users/admin part. — Ed Ford,  DTS Engineer
Jul ’25
App Store rejects binary built with with alternate app icons, ITMS-90895
Hello, At my company, we're trying to run an App Store A/B test on alternate app icons. However, the App Store is rejecting the binary when we upload it (see email below). We're hoping someone out there knows the solution to this issue. Background Currently, our app is built with one target from amongst several different schemes. These schemes are used for various versions, including developer debug builds, TestFlight builds, App Store builds, and others. Each scheme has its own distinct app icon specified in Xcode, as shown in the image below: In our project, we've added the alternate app icons for the two App Store treatments as recommended according to Apple's documentation (we named them AppIcon-T1 and AppIcon-T2). These are located inside our Images.xcassets asset catalog. Each alternate app icon's properties are configured as: iOS: Single Size macOS: None watchOS: None Appearances: None Gamut: Any The Problem After making the changes above, creating an App Store build succeeds as usual. However, every t
4
0
303
May ’25
ITMS-90398: Invalid WatchKit support
Does anyone encounter this email from the Apple Store Connect? Please correct the following issues and upload a new binary to App Store Connect. ITMS-90398: Invalid WatchKit support - The bundle contains architectures that aren’t allowed or is missing architectures that are required. Verify in the Xcode build settings that the architectures on which your app is built are correct. I'm trying to upload my app with a WatchKit app and WatchKit extension. I'm using standard architecture in build setting architectures settings for my iOS, WatchKit app and WatchKit Extension. I also added excluded architecture of armv7 for the iOS and none for the watchkits. The minimum build deployment for iOS is 12.0 and 4.0 for watchOS. Im using Xcode Version 16.4 (16F6)
1
0
80
Jun ’25
Guidance on Java JRE Usage for PST Parsing in Mac OS Application– Code Signing & App Store Compliance
Hello Apple Support Team, We are developing a macOS application that allows users to import and view PST files (Microsoft Outlook archives). These files contain a complex, proprietary format that requires specialized parsing libraries. To achieve this, we are using Aspose Email for Java, which is currently one of the few reliable libraries that support complete PST parsing across platforms. Why we are using Java & Aspose The Aspose Email Java library provides a comprehensive API to extract mail data (including metadata, attachments, and folder structure) from .pst files. A native Swift or Objective-C alternative with full .pst parsing capability does not exist, which is why we opted for a Java-based helper module that runs in the background and communicates with the macOS app over a Unix domain socket. How we bundle it We package the AsposeEmail.jar and a custom JRE (Java Runtime Environment) created using jlink, tailored to run only our jar. This entire setup (JAR + JRE) is bundled within the Contents/Re
6
0
209
Jun ’25
Reply to Guidance on Java JRE Usage for PST Parsing in Mac OS Application– Code Signing & App Store Compliance
Thanks @DTS Engineer and @Etresoft But the exact problem here is something else relating to security issues. I did try the approach of moving it into the PlugIns directory and still App store expected me to codesign all the dylibs and the binaries with entitlements. The problem arises when I had to add the com.apple.security.app-sandbox entitlement to the java executable to avoid thie error. 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: [[com.app.sample.appstore.pkg/Payload/Sample.app/Contents/PlugIns/Java.runtime/Contents/custom-jre-universal/bin/java]] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app. So when i added an entitlement file and codesigned the java executable inside my PlugIns directory and after which when i run the java executable I get this error, which was
Jun ’25