Skip to content

Upload build to App Store #117

Open
Open

Description

@gru2007

For now we can build an app and test it on-device, but uploading to App Store Connect is hard process: fix AppIcon, sign app, upload and more.

So I'm waiting for easy solution for that. This tool is a game changer.

Activity

  1. kvaster commented on Nov 12, 2025

    @kvaster

    What should be done to implement such thing ? Can we already sign app for uploading ?

  2. reinzor commented on Dec 11, 2025

    @reinzor

    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)
    

    Update

    When I set

    <key>DTPlatformName</key>
    <string>iphoneos</string>
    

    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.
    
  3. gru2007 commented on Jan 4, 2026

    @gru2007
    Author
    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

  4. reinzor commented on Jan 19, 2026

    @reinzor

    Yes with SDK 26. Eventually, we ended up doing the following:

    • Manually create a Assets.car via xcrun actool
    • Generate XCode project
    • Add additional build step in XCode that copies the Assets.car

    After these steps, we were able to build and distribute the app via Xcode.

  5. gulian commented on Nov 8, 2026

    @gulian

    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-linux on my fork, https://github.com/gulian/xtool/tree/testflight-linux. It's main at a2875dd with these merged on top:

    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.
    • DT* keys are stamped from Xcode 27.2 and the binary records sdk 27.2 in LC_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 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.

    Smaller notes on #327

    • --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.

  6. TartanLeGrand commented on Nov 8, 2026

    @TartanLeGrand

    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.

    @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.

  7. gulian commented on Nov 8, 2026

    @gulian

    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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions