ITMS-90158

Ha. got an iOS version of the app together. Validated OK. Took a long time to upload but completed OK. Remember this includes the modified model in the app bundle. Got an email from App Store Connect. Please correct the following issues and upload a new binary to App Store Connect. ITMS-90558: Thinned app size is too large - The “/Payload/PK-LLM.app” app bundle in the universal variant is 4 GB, which exceeds the maximum allowable size. Looks like I'm going to upload the specialized model to HuggingFace. Also, the current macOS version give an error after compiling (but not always). Could not launch “PK-LLM” Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. The logs are full of a lot of stuff I don't understand. Maybe uploading to HuggingFace is the way to go.

Thank you for your answer. I tried with both AsheKube.app.a-Shell.localWebServer and com.example.example-extension. The only difference I could see is that sometimes it would fail when uploading (I would get the error message inside Xcode) and other time it would fail after uploading: I would get a kind e-mail from AppStore Connect, stating: Hello, We noticed one or more issues with a recent delivery for the following app: a-Shell App Apple ID 1473805438 Version 1.17.0 Build 500 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90349: Invalid Info.plist value - The value of the EXExtensionPointIdentifier key, AsheKube.app.a-Shell.localWebServer, in the Info.plist of “a-Shell.app/Extensions/localWebServer.appex” is invalid. Please refer to the App Extension Programming Guide at https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Action.html#/apple_ref/doc/uid/TP40014214-CH13-SW1. Apple Developer Relations Builds 496, 497 and

I have previously upload an aar asset with Transporter. The error message after adding the DTPlatform based on the error message ITMS-90508: Invalid Info.plist value - The value for the key 'DTPlatformName' in bundle Spatial Cat Videos.app/Extensions/HostedCatVideos.appex is invalid.

We are having this same issue as combinatorial with the Release version of Xcode 26. Uploading one of our apps will attempt to associate with another app. We get an email with the error ITMS-90055: This bundle is invalid and it lists the bundle id of a different app than the one we uploaded.

I’m facing the following issue while submitting my Flutter iOS app to App Store Connect: ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/Runner.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. My project is a Flutter iOS application that uses a static C++ .a library, which I integrated via a custom .podspec file. However, the project does not contain any Swift code. Could you please help me understand why these Swift libraries are being included in the IPA build? Also, how should I properly configure the Podspec or Xcode proj

It’s part of our own framework, not a third-party dependency. For some reason, the DTPlatformName key is missing from the framework’s Info.plist, which caused the ITMS-90058 error during validation. We resolved this by adding DTPlatformName = iphoneos to the framework’s Info.plist, and the build is now passing App Store checks. Right, you won't find this key in the source Info.plist file for any target in Xcode, because it's expected to be generated as part of the build. The value can vary, as a framework can be built for different platforms, so hardcoding this value into your Info.plist isn't the right long-term solution. To figure out the right solution, are you able to share a stripped down version of your framework project with us, either through a link here to somewhere else on the Internet, or if you need to keep it private, you can open a code-level support request to get me a private copy? The stripped down version here is that I only need to see something that builds, so you could delete mos

I have just tried with Xcode 26 RC and still get the same error ITMS-90717: Invalid large app icon. I have tested with only SVG files, with only PNG, where one was w/o alpha, and with combination SVG and PNG. Nothing worked. I sent feedback with attached AppIcon.icon file.

For guidance, see the following resources: App Privacy Configuration Adding a privacy manifest to your app or third-party SDK Be sure to read Handling ITMS-91061: Missing privacy manifest.