Unsupported SDK or Xcode version (XCode 15.4 running on MacOS 15)

It might be worth checking that you are running the right copy of the xcode tools.

I have the same issue as you, you able to fix this ?

same

im having the same, was trying this fix here https://developer.apple.com/forums/thread/117438

by Go to Organizer Right-Click on your app archive -> show in Finder Right-Click on the .xcarchive -> Show package content Go to Products/Applications/"AppName".app/ Open the info.plist Find the BuildMachineOSBuild and change it to the latest public MacOS release (18F132 for macOS 10.14.5)

Same problem here after updating to Xcode 16 and downgrading afterwards Maybe, we need to install an older macOS? https://forums.macrumors.com/threads/xcode.2428826/

Was able to solve the problem. This problem was caused by macOS 15.0, which I already installed. It did not matter, which xCode version I used. So I organized a cloud access to a Mac (with macOS Sonoma and xCode 15.4) (https://www.macincloud.com), cloned the project from GitHub and archived and sent it to Apple Store connect again. Now, was able to send it to Apple to check it.

I had to create virtual machine with Sonoma , install Xcode 15, then from the main machine with Sequoia but running Xcode 15, ( can be the same done in Xcode 16 this part ) create a provisioning profile, export developer profile from Xcode , export the two certificates I saw on my system keychain access regarding to apple developer. On the virtual machine (Sonoma), import the certificates exported from the keychain , add it to System ( not to login ) , in Xcode, import the developer profile, in the App general, instead of Xcode managing the provisioning profile, select to import and select the provision profile you made at developer.apple.com ( be sure to select iOS , on the devices show all and select all Macs and phones.. and everything ;) Then create the Archive, right click + show in finder. copied the xarchive to my sequoia os machine, and upload from there

TLDR, no need to manage provisioning profile:

1. Share your project folder with the virtual machine
2. Open the project in xcode 15.4 in the virtual machine, do not change anything
3. Click Product->Archive
4. Once done, copy the archive to your physical machine
5. Open the project in your physical machine, and click Window->Organizer, and distribute your app.

If your project doesn't require additional build configurations, you can also use xcode cloud build to simplifiy things.

Any fix without having to do a virtual machine? Since i dont have enough SSD left? Cant believe theres no easier solution to this yet

This worked for me: https://stackoverflow.com/a/78863310/4483446

@12312312211312313122 thank you - this was the only thing that worked for me and I sure as hell am not installing a virtual machine just to get around Apple's shortfalls.

First off, you need the last stable build of Xcode (as of writing, this is 15.4). Now, you can't run this in Sequoia because it says it's not compatible (this is a lie, and we need this version of Xcode).

To run the app:

• Open Terminal
  

• Open Applications folder in Finder
  

• Drag the Xcode app into Terminal so it gets its path
  

• Then add this next to it: /Contents/MacOS/Xcode, so the full command will be something like /Applications/Xcode-12.5.1.app/Contents/MacOS/Xcode
  

• Press enter to run the command
  

When you've got the build archived through Xcode 15.4 do the following:

• From Archives, right click the build, Show in Finder
  

• Right click, Show Package Contents
  

• Products -> Applications -> Right click "App Name", Show Package Contents
  

• Find the Info.plist and open in Xcode
  

• Change BuildMachineOSBuild value to be the latest non-beta MacOS Release, you can find it here: (https://en.wikipedia.org/wiki/MacOS_Sonoma) - e.g 23G93
  

• Save
  

• Distribute normally
  

With all of these steps, I was able to upload my app to review without a virtual machine, while on a beta version of Sequoia.

There is a workaround for Xcode 15.x running on MacOS 15. Just go to the Xcode 15.x folder, show its package content, go to Contents->MacOS, and double click the executable file Xcode. This workaround works perfectly!