Xcode 27.0 Support

[dalexsoto]

WARNING:

Warning

Do not update to macOS 27 until we release support for it, 🚨 macOS 27 does not support Xcode 26.x Series 🚨

🚨 Announcements 🚨

We have released our first preview based on Xcode 27.0 Beta 4, give it a try and let us know!

https://github.com/dotnet/macios/releases/tag/dotnet-10.0.1xx-xcode27.0-P1-10417

Old Announcements, click to expand!

Initial announcement

Xcode 27.0 was announced on June 9th 2026 at WWDC, We will be working on supporting it in the upcoming months. So stay tuned! We will be updating this issue as we make progress on it. For now we do not have Xcode 27.0 supported packages just yet.

---

Release Check List

This is a checklist for what to do for every release.

Copy this list into a new issue and then check off as the release progresses.

✅ Checklist

Xcode 27.0

• Create new milestone in GitHub.
• Create a new issue with a copy of this list, assign it to the milestone.

Beta 1

• Update binding status in wiki (https://github.com/dotnet/macios/wiki/xcode27.0-Bindings-Status)
• Create a new xcodeX[.Y] branch - this needs deciding where to branch from (which is outside the scope of this document). Push this branch to origin with no changes.
• Create PR with an Xcode bump.
  • Update the following values in Make.versions:
    • *_NUGET_OS_VERSION
  • Update the following values in Make.config:
    • XCODE_VERSION
    • XCODE_URL
    • XCODE_DEVELOPER_ROOT
  • Update the xcodeChannel value in tools/devops/automation/templates/variables/common.yml. Change to Beta if using an Xcode beta or release candidate, and switch back to Stable with the final (stable) Xcode release.
  • Add the new OS versions to the builds/Version-*.plist.in files.
  • Build and fix any issues.
  • Run the following tests locally, and fix any issues (these are the ones that typically fail in Xcode bumps, but there may be other failing tests as well - CI will report any such failures once the PR is created):
    • xtro
    • monotouch-test
    • introspection
    • cecil
    • bgen
• Bind APIs!

Beta X

• Update binding status in wiki.
• Create PR with an Xcode bump.
  • Build and fix any issues.
  • Run the following tests locally, and fix any issues (these are the ones that typically fail in Xcode bumps, but there may be other failing tests as well - CI will report any such failures once the PR is created):
    • xtro
    • monotouch-test
    • introspection
    • cecil
    • bgen
• Update any existing API bindings PRs if needed.
• Bind APIs!

Pre-release process

This happens after the stable version of Xcode has been released and the xcodeX[.Y] branch has been updated according to the previous section(s).

• Make sure all the PRs targeting the xcodeX[.Y] branch have been merged and no more changes are desired for the release.
• Merge the xcodeX[.Y] branch into main.
• Merge main into the target release branch (for instance this was release/9.0.1xx for the Xcode 16.4 release).
• Review the API diff to make sure all api differences are expected.
• Make sure the release branch created packages after the merge and pushed them to maestro.
• Create VS insertion (this may not happen for all releases, sometimes we release only to NuGet).
• Let MAUI know about our new package names, so they can update their darc dependencies. For instance, these dependencies: https://github.com/dotnet/maui/blob/408a1cc69d6a120cafa4e75ae30411f1ec48fa3a/eng/Version.Details.xml#L15-L30 would have to be updated to net9.0_18.5 or net9.0_15.5 for our Xcode 16.4 release.

Release process

• Write release notes.
• Publish NuGets to nuget.org.
• Publish release notes.
• Update API diff (the STABLE_NUGET_VERSION_* variables in Make.config) for the main branch. Can only be done after the NuGets have been published to nuget.org.
  • Link to PR
• Update docs by executing docs/sync-mobile-docs.sh. Beware if docs were modified in the docs-mobile repository by somebody else, any such changes will have to be copied back first.
  • Link to dotnet/docs-mobile PR
• Update API / reference docs. See update-api-docs.md for instructions.
  • Create new monikers (add link to dev.azure.com ticket)
  • Add reference docs (add link to dotnet/macios-api-docs PR)
  • Flip the monikers from prerelease to live (add link to dev.azure.com ticket)
• Make sure all items in the milestone for the current release have been closed.
• Close this issue & close the milestone.
• Wonder about life as you consider the impossibility of actually reaching this point, because you can't close the milestone before all issues have been closed, and you can't close this issue until checking off all items, which you can't do until you've closed the milestone. Decide to schedule yet another viewing of Life of Brian to cope celebrate the release 🍾.

[dalexsoto]

We have released our first preview based on Xcode 27.0 Beta 4 https://github.com/dotnet/macios/releases/tag/dotnet-10.0.1xx-xcode27.0-P1-10417 give it a try and let us know!

[dalexsoto]

Do not update to macOS 27 until we release support for it, 🚨 macOS 27 does not support Xcode 26.x Series 🚨

[vhugogarcia]

Thanks @dalexsoto for the heads up. Sadly, macOS was updated last night on my computer. I will keep an eye on this thread. Thanks again for the hard work 🙏🏻

[GlisseManTV]

@dalexsoto you can install the old version of Xcode, which cannot be launched on macos27 but you can compile from this one by cli.
@vhugogarcia https://developer.apple.com/download/all/?q=xcode%2026.6

xcode-select -p
/Applications/Xcode.app/Contents/Developer

It is still using the old one. I renamed the new one as Xcode27 but feel free to do the invert.

You can repath your Xcode with
sudo xcode-select -s /Applications/{Xcode26.6AppName}.app/Contents/Developer

[vhugogarcia]

oh! That is fantastic! I will give me a try @GlisseManTV , thanks for sharing it 🙏🏻

[vhugogarcia]

Hello @GlisseManTV,

so, I did these steps in this order:

1. I downloaded XCode 26.6
2. Renamed XCode.app to XCode27.app from the /Applications
3. Drag and dropped the XCode 26.6 (XCode.app) into the /Applications
4. Executed the terminal command: 'xcode-select -p /Applications/Xcode.app/Contents/Developer'

when trying to run my maui app on VS Code, I get the following: actool error No simulator runtime version from ["24A434"] available to use with iphonesimulator SDK version 23F81a

Maybe because the simulators from version 26.6 were deleted? may I need to reinstall them? I even tried running directly on a physical device without luck.

Update Sept 15, 2026: 6:09 PM CT
I installed the simulators 26.5 and all is back working as expected.

Thank you all for the support!

[christianrr]

The solution of @GlisseManTV, @vhugogarcia worked for me as well:

I downloaded Xcode 26.6, renamed it to Xcode_26.6 and dropped it to /Applications. Next, it was possible to bypass the OS version check and launch it by executing the binary directly in Terminal:

/Applications/Xcode_26.6.app/Contents/MacOS/Xcode
(adapt path accordingly)

On first startup, Xcode 26.6 asked for installing the simulator runtime 26.5.

I then used xcode-select to select the 26.6 version and also switched the Apple Platform in Rider's settings.

sudo xcode-select -s /Applications/Xcode_26.6.app/Contents/Developer

With this setup, I'm able to run and build .NET 10 MAUI apps on macOS 27 with Rider. I haven't uploaded any IPA built this way to the App Store yet, but I assume it should be fine - I'll keep you posted.

The only downside of this solution is that it's not possible to deploy to iOS 27 simulators with this setup.

@dalexsoto I wish I'd read your warning before upgrading. Anyway, could you give a rough estimate of when Xcode 27 support will be released?

[GlisseManTV]

Hi @vhugogarcia I apologize! I had no time to answer until now.
Great that you found a solution!

@christianrr great that you did explain very well the steps.

From my side, I'm only building corporate desktop app for MacOS and Windows in MAUI to keep it simple.
So, In windows I'm using VisualStudio to launch the app and in MacOs I run it through the terminal, without any emulator then.

Glad that my clue helpt you both

@dalexsoto can you please add the workaround (at least the comment link?) into your warning? Because even if you warn users, if update already done they will feel stuck, but it is not.

[christianrr]

Yes, 26.6 simulators (and older simulator runtimes) work. Upload to Testflight via Transporter works as well.