ITMS-90158

Hi, I am facing a problem with Xcode 12.3, swift 5, and cocoapods-1.10.1 version when I want to publish my archive on Appstore Connect, everything goes well, but once the application sent I receive an e-mail from App Store Connect with the following error : ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreLocation.dylib, libswiftAccelerate.dylib, libswiftCoreGraphics.dylib, libswiftCoreData.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftAVFoundation.dylib, libswiftContacts.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftMediaPlayer.dylib, libswiftCloudKit.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/WoWonder.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and

I have seen several posts around the internet from years past with complains of such a problem, the review is rejected with : 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 10.1 and the SDK for iOS 12.1 and watchOS 5.1, Xcode 7.1 and the SDK for tvOS 9, or Xcode 6 and the SDK for macOS 10.9 or later. If you are using an Xcode beta version to test your app, make sure you are using the latest supported version. My XCode is 14.1 and I am using github Continuous integration to build it. Any hint on how can I track what is wrong? Each and every post I found on the subject ended either without any answer or just saying to wait for apple to fix it.

I use the promotion function (https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/promoting_in-app_purchases)) within the app. It worked well up to the iOS15 environment, but during the iOS16 beta test, it was confirmed that it did not work properly. When tested according to the guide (https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/testing_promoted_in-app_purchases)), iOS15 calls paymentQueue:shouldAddStorePayment:delegate normally, but iOS16 does not call paymentQueue:shouldAddStorePayment:. The link used for the test is itms-services://?action=purchaseIntent&bundleId=com.nhn.cloud.client.sdk&productIdentifier=com.nn.cloud.iap.gem99 Is there a problem with iOS16?

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

Hello I have a problem with Xcode when I want to publish my archive on Appstore Connect, everything goes well, but once the application sent I receive an e-mail from App Store Connect with the following error :Dear Developer,We identified one or more issues with a recent delivery for your app, Notorioustrade 1.4 (1). Please correct the following issues, then upload again.ITMS-90424: Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it.Best regards,The App Store TeamConfiguration :Mac Os Mojave 10.14.16Xcode Version 11.2.1 (11B500)My application is a simple WKWebView with cocoapods for OneSignal Notification extension.I really need Help, i have try to call Apple but the services don't know where the problem come from.

From appstore receive email with this issues: ITMS-90738: Invalid purpose string value - The “NSPhotoLibraryUsageDescription” value for the NSPhotoLibraryUsageDescription key isn’t allowed in “.....”. 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 “.....” bundle should contain a NSPhotoLibraryUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. ITMS-90738: Invalid purpose string value - The “NSCameraUsageDescription” value for the NSCameraUsageDescription key isn’t allowed in “....”. 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 “.....” bundle should contain a NSCameraUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. I

I get this error when trying to submit a beta build. App Store Connect Operation Error ERROR ITMS-90334: Invalid Code Signature Identifier. The identifier com.apple.WK in your code signature for app name watch must match its Bundle Identifier com.appname.watchkitapp I don't know of anything that has changed with the code signing since last successful submission, can't find com.apple.WK anywhere in my project and have tried submitting a previous version with no changes and get the same error. Anyone have any idea what I could be doing wrong?

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.

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

So we checked the: Supports running without ios app installation, and it updated our app on the app store. Now we are seeing a lot of instances where our users have one version of the Watch app, and another of the iOS companion app. We have also been collecting a myriad of random crashes, and we can't help but wonder if it's due to these apps being out of sync. We'd like to roll back and test this theory by making the watch app and the iPhone apps dependent on each other again. However, after opting on Apple Connect to Remove from sale, and then Remove app, we cannot push a new version with the change. I get the following error:ERROR ITMS-90768: Invalid Bundle. The watch app '[app]' watch extension must have 'WKWatchOnly' or 'WKRunsIndependentlyOfCompanionApp' Info.plist keys set to 'true', since a version of this app that supports standalone watchOS devices is currently available on the App StoreDoes anyone know a way we can get back to having these apps dependent? Thanks.

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]