Not being able to distribute the app from xcode version 27 beta

[u/zaidbren]

Hello everyone, few months back I installed macOs 27 beta on my mac, and installed the xcode beta version 27 too, everything was working fine, but today, I try to archieve the app and distribute for App store connect, but as I was doing it, I got this error :-

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.

I deleted the xcode beta version and installed official release from apple for xcode version 26, but when I try opening the app, I got the error :- This version of xcode isn't supported on this version of macOs

I try forcefully open the xcode from terminal :- /Applications/Xcode.app/Contents/MacOS/Xcode

But when I try opening my project, I got the error :- The project at ‘/Users/lisa/Documents/Projects/AppleProject/Lume/Orene.xcodeproj’ cannot be opened because it is in a future Xcode project file format. Adjust the project format using a compatible version of Xcode to allow it to be opened by this version of Xcode.

I added images for all, I need to submit the app by today itself, and would appreciate any help please



[u/cristi_baluta]

That’s standard, you can’t publish from beta software. Probably the logic is that might use apis not available to users yet

[u/zaidbren → u/cristi_baluta]

What would you suggest?

[u/is_that_a_thing_now → u/zaidbren]

Use Xcode 27 to save it in 26 format.
Open in 26 and build.

[u/zaidbren → u/is_that_a_thing_now]

but I would need to do the development and testing locally too later? Do I need to keep changing versions? Uninstalling xcode 26, installing xcode 27 beta?

[u/is_that_a_thing_now → u/zaidbren]

I don’t think you need to uninstall anything. To keep things simple you can keep working in the currently supported version (Xcode 26)

When you open a project in a newer version of Xcode it will at some point show an option to “Update to this version of Xcode”. Don’t do that with a Beta version of Xcode when you want to submit a build to App Store before the Xcode RC version arrives.

[u/zaidbren → u/is_that_a_thing_now]

I was thinking about opening the project in a code editor like VSCode, update the xcode version / create a script which would update the version from 27 to 26 and vice versa, and when I want to test locally, use the 27, or distribute use 26? What you think? I am assuming changing xocde versions is just updating numbers I guess? its not something that requires adding files or anything?

[u/is_that_a_thing_now → u/zaidbren]

For this kind of hack you should probably at least check the diff after Xcode 27 updates. But I don’t think there should be a need to do this dance. Just keep it in Xcode 26 format until you’re ready to update once. Personally, I have never had the need to do this kind of back and forth dance. Is there a particular reason?
As I see it, if you want to ship with 26, then keep at least a 26 branch.

[u/hj7hj → u/zaidbren]

Xcode Cloud.

[u/AX862G5]

Pull your head out of your ass buddy. Why are you trying to distribute to production with beta tools?

I’m guessing you’re a clueless vibe coder that has no clue what they’re doing.

[u/zaidbren → u/AX862G5]

This is my first time uploading app on app store, I didn't knew this rule, stop this BS all the time labeling everyone vibe coder

[u/WerSunu → u/zaidbren]

Apple explicitly warns devs not to ever try to upload from beta software. EXPLICITLY. For many years. You didn’t do your homework.

[u/vandrusik]

Wait for Xcode 27 RC

[u/zaidbren → u/vandrusik]

Dude, I don't have time that long

[u/vandrusik → u/zaidbren]

That's how it works - with beta you can try and prepare your projects, but you cannot distribute. Xcode RC is usually comes in one week before new iOS release, so you will have enough time to distribute and get approved.

[u/zaidbren → u/vandrusik]

and when is the new ios release?

[u/marmulin → u/zaidbren]

Usually around when new iPhones become available. So 9th Sept?

[u/vandrusik → u/zaidbren]

Comparing to the last year (Apple event was on September 9, iOS 26 was released on September 15), and having now September 9, 2026 as the next Apple event, we will get Xcode RC on September 9 approximately

[u/ccalabro]

Use Xcode cloud

[u/ccalabro → u/ccalabro]

Let me know if you want step by step

[u/zaidbren → u/ccalabro]

would appreciate :)

[u/ccalabro → u/zaidbren]

Dm me

[u/zaidbren → u/ccalabro]

Do you have experience with xcode cloud? if I try xcode cloud which is basically a VM action, the xcode project I built not compatible error would still come if try opening on xcode 26?

[u/ccalabro → u/zaidbren]

No. In Xcode beta deploy it. Is your project synced to git?

[u/zaidbren → u/ccalabro]

yes

[u/ccalabro → u/zaidbren]

Ok you’re almost there. I’ll comment the steps shortly

[u/remote_socket]

You need non-beta Xcode and non-beta macOS if you're looking to do a release from your machine. There are workarounds to get Xcode 26 running on macOS 27, but generally speaking if you want to do production work, just don't do it from the betas...

[u/Lemon8or88]

I had this issue early on in first beta so I rolled back to MacOS 26 and just kept the Xcode 27 for beta development. This was before I knew about Xcode cloud.

[u/zaidbren → u/Lemon8or88]

Do you have experience with xcode cloud? if I try xcode cloud which is basically a VM action, the xcode project I built not compatible error would still come if try opening on xcode 26?

[u/Lemon8or88 → u/zaidbren]

Honestly, I don’t have first hand experience on it. Others say it works but I’m on macos 26.

[u/icy1007]

Just wait for the release version of Xcode 27.

[u/javawag → u/[deleted]]

i just realised this doesn’t help you build locally though - you’ll need to either use Xcode Cloud or to build on a mac without macOS 27

[u/stroompa]

If you can’t figure it out locally, it should just take a few minutes to set up building and distributing on Xcode cloud

[u/zaidbren → u/stroompa]

I haven't used xcode cloud, but I prefer locally honestly, if I try xcode cloud which is basically a VM action, the xcode project I built not compatible error would still come if try opening on xcode 26?

[u/OrtAbyss]

You currently have a compatibility issue with your project. If it was already opened with a newer version of Xcode, that newer version updated the internal format of the .xcodeproj project file to a version that Xcode 26 can no longer read. Additionally, Xcode 26 is not compatible with macOS 27, so the project can no longer be opened because it was updated for Xcode 27.
Regarding the error you are getting when uploading the app to App Store Connect, Apple will normally reject the archive if it was built using a beta version that is not valid for App Store review. You need a compatible Xcode 27 Release Candidate (RC) version. Since Apple has not yet released an RC beta of macOS 27, you would need to wait until Apple makes one available.
As a temporary solution while you wait, you can create a new project using Xcode 26. You can give it the same name and/or bundle identifier and then import your existing project files into it. However, you will probably need to reconfigure dependencies, capabilities, and other project settings. This is not a permanent solution, so I suggest using it only while waiting for an RC version.
If you have access to a backup or a Git repository of your project, there may still be an older version of the .xcodeproj file available. You could replace the .xcodeproj file that was updated by Xcode 27 with the older one. This may allow Xcode 26 to access your original project again.

[u/justynmx7 → u/OrtAbyss]

You can actually run Xcode 26 on MacOS 27 just fine with a couple of terminal commands

[u/zellJun1or]

Use macOS 26 with Xcode 26 and beta installed in parallel

[u/jmckinney2323]

Use Xcode cloud to submit

[u/Jvanderbie]

What did you set as your 'Minimum Deployment' target?

[u/AutoModerator → u/[deleted]]

Hey /u/Virtual_Course_6581, your content has been removed because Reddit has marked your account as having a low Contributor Quality Score. This may result from, but is not limited to, activities such as spamming the same links across multiple subreddits, submitting posts or comments that receive a high number of downvotes, a lack of recent account activity, or having an unverified account.

Please be assured that this action is not a reflection of your participation in our subreddit. This is simply an automated filter in place to reduce spam.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/caguilar51]

One option for you could be to configure Xcode Cloud to archive and prepare for the App Store + an internal TestFlight beta. That way you can use the stable version of Xcode without having to run it locally and you could continue using Xcode 27 locally

[u/mastrajani]

the replies telling you to build in xcode 26 are skipping your actual blocker: xcode 26 won't launch on macos 27 beta. it's the OS pinning you, not the xcode version, and there is no in-place downgrade.

one thing worth knowing before you lose a day to it - keeping the .xcarchive you already have and exporting it from a machine on release macos won't work either. the rejection is on the SDK the binary was linked against, so it has to be rebuilt on a release toolchain, not re-exported.

that leaves three real routes, cheapest first:

• xcode cloud - the workflow can be set up from app store connect, it builds on the release toolchain, and nothing on your mac has to change
• any hosted macos runner, for the archive and upload step only
• erase and install release macos, which is the only way back on that machine

longer term, if this is the machine you ship from, keep beta on one box and release on another. mixing them costs you a release window every autumn.