Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

App binary rejected - potential XCode back end bug?
Hi, our app - that has been successfully being updated every few weeks on Testflight for years now - suddently (although still compiling and running fine on a device connected to Xcode) fails validation & upload to Testflight. The error message does not give any info, other than Asset validation failed - The app contains one or more corrupted binaries. Rebuild the app and resubmit (ID: 718a52a4-fed6-49ac-a025-8d62f6285cd2). The follow up email, says : We identified one or more issues with a recent delivery for your app, Name of app 1.23 (1.23). 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 you
2
0
1.4k
Dec ’23
An automatic message (ITMS-90338: Non-public API usage) we receive when trying to publish a new version of our apps
Dear Developer, We identified one or more issues with a recent delivery for your app, Oilfield Dispatch 6.1.3 (8). 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 Actually, just small changes in the new app buld (UI and minor improvements). And the same issue for the other our apps (Bunle IDs: ca.riger.mobile, us.riger.sales, us.riger.operations, us.riger.purchases, us.riger.servicecalls) (deploying without any issue
0
0
415
Dec ’23
ITMS-90895: Missing Icon - No such asset is present in the asset catalog.
I have added an alternate icon in my iOS app which I am setting using setAlternateIcon method. It works perfectly during development and local app distribution, however when I try to upload a build to App Store Connect, I get the following error: ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “AppIconTwo” that references asset “AppIconTwo” No such asset is present in the asset catalog. I'm unable to upload builds with this extra app-icon added. Kindly help me solve this.
3
0
1.3k
Nov ’23
Reply to Unable to Add for Review - Xcode 15.0.1 - New apps and app updates must be built with the public (GM) versions of Xcode 11 or later
Anyone still facing this issue? Try the following solution. Somehow I've also selected older version in the project format make sure to select xcode15 or whatever latest. https://stackoverflow.com/questions/44323009/cant-submit-apps-to-appstore-error-itms-90534-invalid-toolchain
Nov ’23
ITMS-90626: Invalid Siri Support - No example phrase was provided for INSearchForMessagesInten
I've gotten the following error message a few times, does anyone know anything about it? I currently have a WidgetExtension and am suspecting that this is the circle. Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90626: Invalid Siri Support - No example phrase was provided for INSearchForMessagesIntent in the 'en' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - No example phrase was provided for INSetMessageAttributeIntent in the 'ko' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - No example phrase was provided for INSetMessageAttributeIntent in the 'en' language. Please refer to 'https://developer.apple.com/documentation/sir
0
0
1.1k
Nov ’23
SAP MDK based iOS App + ITMS-90338: Non-public API usage
Hi Experts, Our first version of app went fine on App Store Connect and we are testing app through TestFlight without any issues. Status = Preparing for submission. When we uploaded the second version 2 days back, suddenly we are getting the following error through email while uploading. Mac OS: Ventura 13.6.1 XCode = 15.0.1 Dear Developer, We identified one or more issues with a recent delivery for your app, YYYYYYYY 1.0.2 (2). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in **Frameworks/SAPMDC.framework/SAPMDC: setNumberOfRowsInSection:.** 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 Inf
0
0
557
Nov ’23
ITMS-90428: Invalid Swift Suppor
I am trying to upload a new build of my app from the new Xcode 15.0.1 but it keeps failing with the below error: ITMS-90428: Invalid Swift Support - The files libswiftMetal.dylib, libswiftCoreGraphics.dylib, libswiftCoreLocation.dylib, libswiftObjectiveC.dylib, libswiftCoreAudio.dylib, libswiftos.dylib, libswiftDarwin.dylib, libswiftsimd.dylib, libswiftFoundation.dylib, libswiftCoreImage.dylib, libswiftQuartzCore.dylib, libswiftNetwork.dylib, libswiftUIKit.dylib, libswiftCoreFoundation.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftDispatch.dylib, libswiftAVFoundation.dylib don’t match /Payload/goodville.app/Frameworks/libswiftMetal.dylib, /Payload/goodville.app/Frameworks/libswiftCoreGraphics.dylib, /Payload/goodville.app/Frameworks/libswiftCoreLocation.dylib, /Payload/goodville.app/Frameworks/libswiftObjectiveC.dylib, /Payload/goodville.app/Frameworks/libswiftCoreAudio.dylib, /Payload/goodville.app/Frameworks/libswiftos.dylib, /Payload/goodville.app/Frameworks/libswiftDarwin.dylib, /Pa
2
0
637
Nov ’23
Reply to Signing and sandbox errors when submitting a Qt mac app. Please help!!
I'm not sure if it's actually possible to publish a Qt app in the Mac App Store. It definitely is; I’ve worked with a bunch of developers in similar situations to you. There are limits to how much I can help you with this. All I can do is explain the requirements imposed by Apple’s distribution channels. When working with third-party tooling, it’s up to the tool’s vendor to explain how best to meet those requirements with their tools. You can find my general advice on this topic in: Creating Distribution-Signed Code for Mac Packaging Mac Software for Distribution after I uploaded to Apple Store Connect through the Organizer, I'd get an email with errors, ITMS-90238: Invalid Signature, mentioning a long list of plugins, and then ITMS-90296: App sandbox not enabled. App Store Connection requires that: All your code be signed with your Apple Distribution signing identity [1] Every executable have the App Sandbox enabled I suspect that your deployment processing has failed to re-sign some of the
Oct ’23
Signing and sandbox errors when submitting a Qt mac app. Please help!!
Hi everyone, I've been trying for a few days and still getting the same errors..so any help would be appreciated!! I've got the app to pass the Validation in XCode Organizer, but after I uploaded to Apple Store Connect through the Organizer, I'd get an email with errors, ITMS-90238: Invalid Signature, mentioning a long list of plugins, and then ITMS-90296: App sandbox not enabled. I'm not sure how to investigate these problems, so I've been just blindly trying everything. I've added the Sandbox capability in Xcode and have the entry in the entitlement file. The app even shows Sandbox Yes in Activity Monitor. This is an Qt app. I generated an Xcode project using qmake, then use Xcode to sign and upload. I tried both manually selecting the profile and letting Xcode manage signing automatically. I've tried both Distribution profiles and Development profiles. It was giving build errors in signing unless I used the --deep flag in Other Code Signing Flags. Then I read online that it's not recommen
9
0
1.4k
Oct ’23
ITMS-90999: Invalid executable - The executable in “xxx.app” contains multiple segments with the executable permission bit set when it should only contain one. After you’ve corrected the issues, you can upload a new binary to App Store Connect.
issue: ITMS-90999: Invalid executable - The executable in “xxx.app” contains multiple segments with the executable permission bit set when it should only contain one. After you’ve corrected the issues, you can upload a new binary to App Store Connect. we use Xcode 14.2 and Xcode 14.3.1 both meet the same problem today(with previous uploaded code to archive and upload also with code 90999).How does it happen? And we do not meet the error code ITMS-90999 at last week.
3
0
2.7k
Oct ’23
Problems submitting an App Clip with size above 15mb (for digital invocations)
We're trying to submit an App Clip with around 17mb, aiming to fit in the new size limit for digital invocations. The mention for the rules can be found in this article.. The relevant part is: If you make your App Clip available on devices running iOS 16.4 and later, your App Clip can be up to 50 MB in size if it meets the following conditions: The App Clip only supports digital invocations — for example, from your website or Spotlight search — and not from physical invocations but like App Clip Codes, QR codes, or NFC tags People use your App Clip in situations where a reliable internet connection is likely, for example, at home Your App Clip doesn’t support iOS versions prior to iOS 16.4 We have updated our App Clip target to have a minimum supported version to iOS 16.4 but when we push it to TestFlight we get an error like below: We identified one or more issues with a recent delivery for your app, (...) Please correct the following issues, then upload again. ITMS-90865: Thinned app clip size is t
2
0
1.5k
Oct ’23
All attempts to upload .ipa via iTMSTransporter failing with error in validateAssets method (1272)
We publish many apps using our CI/CD system that makes use of the App Store Connect API and iTMSTransporter. Since around 9:00am on 19 Oct 2023 (Melbourne/Australia time UTC+10), all our attempts to upload our .ipa files using iTMSTransporter began failing. The specific command line invocation is: /usr/local/itms/bin/iTMSTransporter -m upload -v eXtreme -f /path/to/Bundle.itmsp -jwt {jwt-here} The error is occurring in the midst of the upload with the error message: Apple's web service operation return value: [2023-10-20 09:35:09 AEDT] DBG-X: parameter Errors = [An error occurred while trying to call the requested method validateAssets. (1272)] [2023-10-20 09:35:09 AEDT] DBG-X: parameter RestartClient = false [2023-10-20 09:35:09 AEDT] DBG-X: parameter ErrorCode = 1272 [2023-10-20 09:35:09 AEDT] DBG-X: parameter ErrorMessage = An error occurred while trying to call the requested method validateAssets. (1272) [2023-10-20 09:35:09 AEDT] DBG-X: parameter Success = false [2023-10-20 09:35:09 AEDT]
2
0
877
Oct ’23