You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am also interested in to the process of getting my app ready for the app store. We currently do:
Build app: xtool dev build --configuration release --ipa
Install app on device: xtool install my_app.ipa
This works fine. However, when we try to resign the app using fastlane sigh resign for example and try to upload to the app store using Transporter, we get the following error:
Missing Info.plist value. A value for the key 'DTPlatformName' in bundle App.app is required. (ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
in my Info.plist, I get the following message when uploading:
Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases.
Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases.
@reinzor hmm… have you tried building with SDK 26?
If you have, then there is a problem with difference in Xcode and xtool builds
I got a build from Linux onto TestFlight and installed it on a device, using the open PRs for this issue. Writing down what worked and what didn't, in case it helps get them merged.
Three merge conflicts, all mechanical (DarwinSDK.swift between #321 and #323, the docs index between #326 and #327, Package.swift and Packer.swift between #325 and the rest). One fix of my own: #327 no longer builds on current main because Console moved to XCLIUtils, so UploadCommand.swift needs import XCLIUtils (afc286a).
Host: Ubuntu x86_64, Swift 6.4.1, Darwin SDK from Xcode 27.2 (27B52), xtool built in debug. Test app: Examples/TFLab in the branch, a one-screen SwiftUI app with a single-size AppIcon in an asset catalog.
What works
xtool dev build --configuration release --ipa --p12 … --profile … with an Apple Distribution certificate and an App Store profile I created through the API. xtool upload --check finds nothing to complain about.
xtool sign on an .ipa built elsewhere, and xtool upload, both fine. When Apple rejects a build, the error shows up in about a minute.
A missing BuildMachineOSBuild was not a problem.
What doesn't: the AssetKit Assets.car
Every .ipa built entirely by xtool upload fine and then sit in PROCESSING forever, with no error and no warning. My first three were still stuck after more than two hours.
To find out why, I built the same app with Xcode 26.6 on a GitHub macOS runner (unsigned, workflow .github/workflows/tflab-xcode.yml in the branch), then swapped files between the two .ipas. Each one was signed with xtool sign and sent with xtool upload:
Build
Contents
Result
41
Xcode app, xtool binary
VALID
42
xtool app, Xcode binary
stuck
43
Xcode app, AssetKit Assets.car
stuck
44
xtool app, actool Assets.car
VALID
45
xtool everything except Assets.car (actool's)
VALID, installed through TestFlight and launched on an iPhone
So the AssetKit catalog is the only blocker left. This matches what @TartanLeGrand found in xtool-org/AssetKit#3, independently: a minimal app, a different SDK (27.2), and the same symptom. Until that's fixed, swapping in an Assets.car compiled once by actool, then re-signing with xtool sign, gets a Linux build onto TestFlight.
--wait gives up after 30 minutes. That's fine for a valid build, which took 5 to 10 minutes here, but on this silent hang it exits with a timeout rather than saying anything useful. Maybe worth a hint in the message that a build stuck in PROCESSING has been seen with AssetKit catalogs.
The local check is helpful. It could also flag a missing UISupportedInterfaceOrientations~ipad when UIDeviceFamily includes iPad (ITMS-90474). xtool sets it, but my Xcode reference build didn't, and that was the one rejection I got.
Full disclosure: I ran this experiment with an AI coding assistant (Claude Code) doing most of the hands-on work: merging, building and the bisection. I checked the results myself, including the install on my phone.
Thanks a lot @gulian, this is exactly the end-to-end check these PRs were missing: distribution signing (#326), the SDK keys (#321, #323) and xtool upload (#327), all accepted by App Store Connect with a binary built on Linux, and an install through TestFlight.
xtool: add upload command for App Store Connect #327: you're right, it no longer builds since Console moved to XCLIUtils. I'm updating it on current main, and adding your two suggestions: a --wait timeout message that says the build is still PROCESSING and mentions asset catalogs, and an ITMS-90474 check for a missing UISupportedInterfaceOrientations~ipad on iPad apps.
@kabiroberai with this report, #321, #323, #326 and #327 have now been validated together on a real TestFlight upload, if that helps prioritise the review.
Update: the Assets.car blocker is found and fixed. Two things in how AssetKit writes the BOM trees (the key length in tree headers, and the key copy in each leaf). With them, a build made entirely by xtool on Linux goes through App Store Connect and installs from TestFlight, icon included. Details, the .ipa matrix and the branches: xtool-org/AssetKit#3 (comment)
Activity
kvaster commentedon Nov 12, 2025
What should be done to implement such thing ? Can we already sign app for uploading ?
reinzor commentedon Dec 11, 2025
I am also interested in to the process of getting my app ready for the app store. We currently do:
xtool dev build --configuration release --ipaxtool install my_app.ipaThis works fine. However, when we try to resign the app using
fastlane sigh resignfor example and try to upload to the app store using Transporter, we get the following error:Update
When I set
in my Info.plist, I get the following message when uploading:
gru2007 commentedon Jan 4, 2026
@reinzor hmm… have you tried building with SDK 26?
If you have, then there is a problem with difference in Xcode and xtool builds
reinzor commentedon Jan 19, 2026
Yes with SDK 26. Eventually, we ended up doing the following:
xcrun actoolAfter these steps, we were able to build and distribute the app via Xcode.
gulian commentedon Nov 8, 2026
I got a build from Linux onto TestFlight and installed it on a device, using the open PRs for this issue. Writing down what worked and what didn't, in case it helps get them merged.
Setup: branch
testflight-linuxon my fork, https://github.com/gulian/xtool/tree/testflight-linux. It'smainat a2875dd with these merged on top:46a0206) linker-isysrootc09ce77) DT* keys from the SDKff04d51) distribution signing46f71aa)xtool uploadc1e7683) asset catalogs with AssetKitThree merge conflicts, all mechanical (
DarwinSDK.swiftbetween #321 and #323, the docs index between #326 and #327,Package.swiftandPacker.swiftbetween #325 and the rest). One fix of my own: #327 no longer builds on currentmainbecauseConsolemoved toXCLIUtils, soUploadCommand.swiftneedsimport XCLIUtils(afc286a).Host: Ubuntu x86_64, Swift 6.4.1, Darwin SDK from Xcode 27.2 (27B52), xtool built in debug. Test app:
Examples/TFLabin the branch, a one-screen SwiftUI app with a single-size AppIcon in an asset catalog.What works
xtool dev build --configuration release --ipa --p12 … --profile …with an Apple Distribution certificate and an App Store profile I created through the API.xtool upload --checkfinds nothing to complain about.sdk 27.2inLC_BUILD_VERSION, so packer: pass -isysroot to clang when linking #321 and packer: stamp Apple build keys (DT*) from the SDK #323 do their job. App Store Connect accepted the Linux-built binary with those keys.xtool signon an.ipabuilt elsewhere, andxtool upload, both fine. When Apple rejects a build, the error shows up in about a minute.BuildMachineOSBuildwas not a problem.What doesn't: the AssetKit
Assets.carEvery
.ipabuilt entirely by xtool upload fine and then sit inPROCESSINGforever, with no error and no warning. My first three were still stuck after more than two hours.To find out why, I built the same app with Xcode 26.6 on a GitHub macOS runner (unsigned, workflow
.github/workflows/tflab-xcode.ymlin the branch), then swapped files between the two.ipas. Each one was signed withxtool signand sent withxtool upload:Assets.carAssets.carAssets.car(actool's)So the AssetKit catalog is the only blocker left. This matches what @TartanLeGrand found in xtool-org/AssetKit#3, independently: a minimal app, a different SDK (27.2), and the same symptom. Until that's fixed, swapping in an
Assets.carcompiled once by actool, then re-signing withxtool sign, gets a Linux build onto TestFlight.Smaller notes on #327
--waitgives up after 30 minutes. That's fine for a valid build, which took 5 to 10 minutes here, but on this silent hang it exits with a timeout rather than saying anything useful. Maybe worth a hint in the message that a build stuck inPROCESSINGhas been seen with AssetKit catalogs.UISupportedInterfaceOrientations~ipadwhenUIDeviceFamilyincludes iPad (ITMS-90474). xtool sets it, but my Xcode reference build didn't, and that was the one rejection I got.Full disclosure: I ran this experiment with an AI coding assistant (Claude Code) doing most of the hands-on work: merging, building and the bisection. I checked the results myself, including the install on my phone.
TartanLeGrand commentedon Nov 8, 2026
Thanks a lot @gulian, this is exactly the end-to-end check these PRs were missing: distribution signing (#326), the SDK keys (#321, #323) and
xtool upload(#327), all accepted by App Store Connect with a binary built on Linux, and an install through TestFlight.Consolemoved toXCLIUtils. I'm updating it on current main, and adding your two suggestions: a--waittimeout message that says the build is stillPROCESSINGand mentions asset catalogs, and an ITMS-90474 check for a missingUISupportedInterfaceOrientations~ipadon iPad apps.Assets.car: your swap table matches what I saw on feat(car): match the structure of actool 26.5 output AssetKit#3 with a different app and SDK, so it's a solid confirmation that the catalog is the last blocker. I'll take it to AssetKit, where Add CSI color support and per-size app icon indexing AssetKit#5 is also reworking the same structures.@kabiroberai with this report, #321, #323, #326 and #327 have now been validated together on a real TestFlight upload, if that helps prioritise the review.
gulian commentedon Nov 8, 2026
Update: the
Assets.carblocker is found and fixed. Two things in how AssetKit writes the BOM trees (the key length in tree headers, and the key copy in each leaf). With them, a build made entirely by xtool on Linux goes through App Store Connect and installs from TestFlight, icon included. Details, the.ipamatrix and the branches: xtool-org/AssetKit#3 (comment)