Hi, When submitting manually signed macOS apps then this warning is shown after submission: WARNING ITMS-90889: Cannot be used with TestFlight because the bundle at is missing a provisioning profile. Main bundles are expected to have provisioning profiles in order to be eligible for TestFlight. I use the following commands for signing the app: export VM_CERTIFICATE=Apple Distribution codesign --deep -f -s $VM_CERTIFICATE -v --entitlements $VM_SOURCE_PATH/macos/App.entitlements $VM_APPNAME productbuild --component $VM_APPNAME /Applications --sign 3rd Party Mac Developer Installer: MyCompany outmac.pkg How can I get rid of the warning, so that the package can be used in TestFlight? Regards,
Search results for
ITMS-90158
1,686 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I built and submitted a react-native app using expo eas build -p ios --auto-submit and the app was sent to Apple for submission. I received an email back 5 minutes later that reads: Dear Developer, We identified one or more issues with a recent delivery for your app, react-chipsapp 0.1.2 (0.1.2). Please correct the following issues, then upload again. ITMS-90748: ${message} Best regards, The App Store Team The ${message} looks like a template placeholder that isn't populated and thus there is no information indicating what might be wrong. I google searched for the specific error code and could not find anything. What does this code mean and why is my app submission failing?
After tireless trials research and builds, i came to fix this ITMS-90748: ${message} issue by aligning my bundleIdentifier with the bundleindentifier on Appstore connect secondly on the i populated the submit seccion of eas.json for react native. For any other framework just change only the bundleIdentifier https://docs.expo.dev/submit/eas-json/#appleid
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
We received this error after submitting to apple connect today. How can we resolve this issue? Dear Developer, We identified one or more issues with a recent delivery for your app, ****** 1.14 (33). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in ErgoAuditor: 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 http://developer.apple.com/support/technical/ Best regards, The App Store Team
When I go to upload my app to iTunes (like I've done successfully before), it now gives me an ERROR ITMS-90023: Missing required icon file. The bundle does not contain an app icon for iPad of exactly '76x76' pixels, in .png format for iOS versions >= 7.0.However, the icon file IS there, and the reference to it in plist appears to be correct. What am I missing? What should I check, in what order? I'm not a native Mac user. I'm a windows developer, using Cordova to build mobile apps. I only use the Mac for Apple deployments.On a secondary rant... I can put out an Android AND website release in 5 minutes, but end up spending HOURS on the Apple deployments. Why can't Apple just scale the icon by default and allow overrides for specific resolutions? I'm sure we can find a college freshman to explain image scaling to them. This requiring dozens of icon files is ridiculous. I'm now on my 2nd DAY of trying to fix the Apple deploy. Somebody help!-- one very frustrated developer
We received this error after submitting to apple connect today. How can we found these Non-Public API. Thanks for your help. Dear Developer, We identified one or more issues with a recent delivery for your app, ******** 1.7.3 (73). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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/ Best regards, The App Store Team
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Review
App Store Connect
Xcode
App Submission
Using Flutter ... has anyone seen these app-store errors: ITMS-90036: This bundle is invalid - The Info.plist file for /Payload/Runner.app/Frameworks/App.framework/flutter_assets/packages/st_ui_builder/build/ios/Debug-iphonesimulator/App.framework is missing or could not be read. ITMS-90207: Invalid Bundle - The bundle at '/Payload/Runner.app/Frameworks/App.framework/flutter_assets/packages/st_ui_builder/build/ios/Debug-iphonesimulator/App.framework' does not contain a bundle executable. The IPA validates just fine on my local M1. I only get these errors after upload to Apple and I can’t find the problem with my build-pipeline
When I try to create a TestFlight build of my app using Xcode Cloud, I get a couple of ITMS-90334 errors and the build fails. The error messages look like: ITMS-90334: Invalid Code Signature Identifier - The identifier 'MySwiftPackage-55554944e95A2da4fe9e3357b44de57c3ba890e8' in your code signature for 'MySwiftPackage_-658550CFFF128C8B_PackageProduct' must match its Bundle Identifier 'MySwiftPackage' Where MySwiftPackage is a Swift Package which is used by a framework as well as the application. The dependencies look like this: MyApp + MyFramework + MySwiftPackage + MySwiftPackage MyApp is a macOS app MyFramework is a mixed Swift and Objective-C framework MyApp is also mixed Swift and Objective-C When I run an archive build on my local Mac and upload the build to App Store Connect to be used as a TestFlight build, everything seams to be fine and the build is accepted I found some discussions on ITMS-90334 but not related to using Swift Packages and Frameworks Any ideas what might be
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Developer Tools
Code Signing
TestFlight
Xcode Cloud
macOS 13.1 beta 4 addresses the issue creating ITMS-90334: Invalid Code Signature Identifier in Xcode Cloud. No update to Xcode is necessary to address the issue. This beta was released yesterday, and is available in Xcode Cloud when you configure a workflow to specify the macOS version used to execute your build. As this version is currently a beta, it is only available as part of the Latest Beta or Release macOS configuration, or as a dedicated choice for the macOS version, at this time. If you find this issue is not addressed with this configuration change to your Xcode Cloud workflow, continue to provide us feedback through Feedback Assistant, and share the FB numbers here so I can follow up on them.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
when i upload the ios app i got the error ERROR ITMS-90086: Missing 64-bit support. Beginning on February 1, 2015 new iOS apps submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK. Beginning June 1, 2015 app updates will also need to follow the same requirements. To enable 64-bit in your project, we recommend using the default Xcode build setting of “Standard architectures” to build a single binary with both 32-bit and 64-bit code. how to solve it?
On repetitive attempts, I am getting Invalid Binary with ITMS-90117: Missing routing app coverage file: You must upload a routing app coverage file in App Store Connect if you register as a routing app. Here is my Geo Json file: { type: MultiPolygon, coordinates: [ [[[-141.1,43.7], [-141.1,69.7], [-52.3,69.7], [-52.3,43.7], [-141.1,43.7]]], [[[-127.2,22.9], [-127.2,49.4], [-58.5,49.4], [-58.5,22.9], [-127.2,22.9]]], [[[2.2,49.3], [2.2,51.3], [6.5,51.3], [6.5,49.3], [2.2,49.3]]], [[[59.0625,4.915832801313164], [100.546875,4.915832801313164], [100.546875,38.8225909761771], [59.0625,38.8225909761771], [59.0625,4.915832801313164]]] ] } I just include 3 countries - USA, Canada and India, as I selected these 3 countries AppStore to list my app. Can you please help me what is wrong with the above file? I don't get any error and there is no way to debug this. Thanks
I keep getting emails saying my app cant be processed, how can I fix it or find out whats causing it. Dear Developer, We identified one or more issues with a recent delivery for your app, EmbryosIOS 0.1 (0.99). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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/ Best regards, The App Store Team
Hi, Received a message from apple regarding my app delivery. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.,The app contains one or more corrupted binaries. Rebuild the app and resubmit.,The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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/ Ran build and analyze no issues found Also did a Validate archive before submitting
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
App Review
App Store
App Submission
TestFlight
ReDeploying an App today after a deployment yesterday. No changes to the build. Receiving this error message below, however no binaries are listed as corrupted in the error message.. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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. Any help would be appreciated.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
iOS
App Store Connect
Debugging
TestFlight
We started receiving this error a few days ago when it appeared to be a wide spread problem on Apple's end. https://developer.apple.com/forums/thread/127678?answerId=715975022#715975022 Although it is supposedly resolved, I am still getting this error. I have incremented build and version numbers along with tweaking code. Also, the build agent is running macOS 12.4 and Xcode 13.4.1. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.,The app references non-public selectors in Align-Dev: isActivated. 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/ The only
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Review
App Store Connect
iOS