Fix guide · updated 2026-11-12
Upload your iOS app to the App Store without a Mac (from Windows)
Transporter for Windows not working · no Mac to upload the .ipa · how to upload an ipa without a Mac
Your app is built and you have the .ipa file, but every tutorial ends with "open Transporter on your Mac". You don't need a Mac for this step. Apple's own Upload builds page lists four ways to send a build: Xcode, Transporter for Mac, altool (also Mac) and the App Store Connect API. The API is a set of web requests, so it works from Windows or Linux. That page no longer lists a Windows Transporter, which is probably why the one you found doesn't work.
Check three things first
If one of these is wrong, Apple refuses the file even when the upload itself works.
- The .ipa is signed for App Store distribution, not for development or ad hoc testing. If your builder made the file, ask them which certificate and profile they used.
- The app exists in App Store Connect (Apps → + → New App) with the same bundle ID as the .ipa, and the version and build number are ones you haven't uploaded before.
- It was built with a recent Xcode. Apple's upload page says iOS apps must be built with Xcode 26 or later. A file made with an older Xcode is refused, wherever you upload it from.
Step 1: make an API key
In App Store Connect, open Users and Access, then the Integrations tab, then App Store Connect API in the left column. Stay on Team Keys and click Generate API Key (or +). Give it a name and the App Manager role.
Download the private key right away. It's a .p8 file, and Apple lets you download it only once. Also note the Key ID and the Issuer ID shown on the same page. Treat the .p8 file like a password: anyone who has it can act on your account. Never paste it into a chat, a public repo or a website.
You also need your app's ID: the number shown as Apple ID under App Information.
Step 2: the token
Every call carries a short token signed with your .p8 key: the header Authorization: Bearer <token>. Apple's rules for it:
- Header:
alg=ES256,kid= your Key ID,typ=JWT. - Payload:
iss= your Issuer ID,iat= now,exp= at most 20 minutes later,aud=appstoreconnect-v1.
Any JWT library makes it in a few lines: PyJWT in Python, jose or jsonwebtoken in Node. Make a fresh token for each step if your upload takes long.
Step 3: the three upload calls
All three go to https://api.appstoreconnect.apple.com. First, create a build upload, with your version, build number and app ID:
POST /v1/buildUploads
{"data": {"type": "buildUploads",
"attributes": {"cfBundleShortVersionString": "1.0", "cfBundleVersion": "7", "platform": "IOS"},
"relationships": {"app": {"data": {"type": "apps", "id": "YOUR_APP_ID"}}}}}
Second, reserve the file. Use the build upload's id from the first answer, plus the file's exact name and size in bytes:
POST /v1/buildUploadFiles
{"data": {"type": "buildUploadFiles",
"attributes": {"fileName": "MyApp.ipa", "fileSize": 48211234, "assetType": "ASSET", "uti": "com.apple.ipa"},
"relationships": {"buildUpload": {"data": {"type": "buildUploads", "id": "BUILD_UPLOAD_ID"}}}}}
The answer contains uploadOperations, a list of pieces. Each piece gives a method, a url, an offset, a length and requestHeaders. For each one, send that slice of your file (from offset, length bytes) to that URL, with exactly the headers listed for it.
Third, tell Apple the file is complete:
PATCH /v1/buildUploadFiles/FILE_ID
{"data": {"type": "buildUploadFiles", "id": "FILE_ID", "attributes": {"uploaded": true}}}
Step 4: wait for processing, then submit
Read GET /v1/buildUploads/BUILD_UPLOAD_ID every minute or so. Its state shows the progress, plus any errors and warnings. When processing is done, the build appears under TestFlight in App Store Connect. From there it's the usual path: test it, add it to a version, submit for review.
If Apple refuses the build
- Signing errors: the file was signed for development or ad hoc. It has to be rebuilt with an App Store distribution profile.
- Bundle ID or app not found: the app ID in the first call doesn't belong to the .ipa's bundle ID.
- Build number already used: raise
cfBundleVersionin the app, rebuild, and use the new number in the first call. - SDK or Xcode too old: the builder has to rebuild with Xcode 26 or later. No upload method gets around that.
- 401 on every call: the token. Check the Key ID, the Issuer ID,
aud, and thatexpis at most 20 minutes afteriat. Also check that your computer's clock is right.
Rather not write code?
Build services with Macs in the cloud can do the same upload with the same API key: GitHub Actions, Codemagic, or Expo's EAS for Expo apps. They need a bit of setup, and the free tiers have limits. If your builder offers its own "publish to App Store" button, try that first.
Still stuck after all this? Send us the project and we'll find it.
Sources: Apple Developer, Upload builds, Create a Build Upload, Create a Reservation for a Build Upload File, Commit a Build Upload File, Creating API Keys for App Store Connect API and Generating Tokens for API Requests.
Other problems with an AI-built app? See Vibe code rescue.