I get this error in Visual Studio after updating macOS and Xcode: This version of .NET for iOS (26.0.11017) requires Xcode 26.0. The current version of Xcode is 27.0.

Question

I get this error in Visual Studio after updating macOS and Xcode: This version of .NET for iOS (26.0.11017) requires Xcode 26.0. The current version of Xcode is 27.0.

Mr_K 0

I get this error in Visual Studio Community 18.12.0 after updating macOS(27.2.1) and Xcode(27.0):

This version of .NET for iOS (26.0.11017) requires Xcode 26.0. The current version of Xcode is 27.0. Either install Xcode 26.0, or use a different version of .NET for iOS. See https://aka.ms/xcode-requirement for more information.

I use the following settings for my iOS project in Visual Studio:

Target framework: .NET 10.0

Target OS: 26.0

Supported OS version: 18.0

And I installed the NuGet packages Microsoft.Maui.Controls(11.0.0), Microsoft.Maui.Core(11.0.0) and Microsoft.Maui.Essentials(11.0.0) today in my iOS project.

PS C:\MyProjects\TestProject> dotnet --list-sdks 9.0.306 [C:\Program Files\dotnet\sdk] 9.0.308 [C:\Program Files\dotnet\sdk] 11.0.100 [C:\Program Files\dotnet\sdk]

PS C:\MyProjects\TestProject> dotnet workload list
Workload version: 11.0.100-manifests.5d612b92
Installed Workload Id      Manifest Version         Installation Source
----------------------------------------------------------------------------------------
android                    37.2.29/11.0.100         VS 18.12.12405.243, VS 17.14.36717.8
ios                        27.2.11039/11.0.100      VS 18.12.12405.243, VS 17.14.36717.8
maccatalyst                27.2.11039/11.0.100      VS 18.12.12405.243, VS 17.14.36717.8
maui-windows               11.0.0/11.0.100          VS 18.12.12405.243, VS 17.14.36717.8

How can I solve the issue? Is it not yet possible to use Xcode 27.0 for debugging my iOS project?

0 comments

3 answers

Your answer

Answer 1

Nguyen Dam (WICLOUD CORPORATION) 1,335 Microsoft External Staff Moderator

Hello @Mr_K and thank you for reaching out.

The error occurs because your project is currently using .NET for iOS 26.0.11017, which requires Xcode 26.0.

To use Xcode 27.0, please install the latest .NET 10 SDK and update its corresponding .NET for iOS workload to a version that supports Xcode 27.0, as documented in the release notes:

Xcode 27.0 is required with this release. Xcode 27.0 requires macOS 26.6+ (Tahoe).

The .NET MAUI Dev Blog also confirms:

At the time of writing, the released .NET 10 iOS and Mac Catalyst workloads 27.0.10722 require Xcode 27.0.

After updating, please rebuild your project. If you encounter any further issues, please feel free to raise them.

If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation. Thank you.

Mr_K 0 Reputation points

2026-11-12T10:39:30.01+00:00

To use Xcode 27.0, please install the latest .NET 10 SDK and update its corresponding .NET for iOS workload to a version that supports Xcode 27.0, as documented in the release notes:

I still get the same error after updating. In addition, I have tried Clean and Rebuild my iOS project.
Nguyen Dam (WICLOUD CORPORATION) 1,335 Reputation points Microsoft External Staff Moderator

2026-11-12T10:57:58.02+00:00
Hello @Mr_K

I appreciate the update.

Although this may be a bit repetitive, I would appreciate it if you could confirm whether the .NET 10 SDK now appears in the output of dotnet --list-sdks, since your original output listed .NET 9 and .NET 11, but not .NET 10.

Then run the following command from the project directory:

dotnet build -f net10.0-ios -bl

Please let me know if the command-line build reports the same 26.0.11017 error.

Other suggestions:

Please check whether a global.json file exists in the solution directory or any parent directory, as it may cause the build to select a different SDK version.

Temporarily, add the following property to the project file to bypass Xcode version check

<ValidateXcodeVersion>false</ValidateXcodeVersion>

If the command-line build succeeds but Visual Studio still reports the error, the issue is likely specific to the SDK or workload being selected by Visual Studio.

That said, any additional details you can share about the results would help us better understand what might be causing the issue.

Answer 2

Bruce (SqlWork.com) 85,786

As you updated MacOs to Golden Gate, Xcode 26 is not supported. You will need to update your Maui workload to 10.0.100 or higher for Xcode 27 support.

also read the release notes as Xcode 27 support requires source code changes.

https://devblogs.microsoft.com/dotnet/migrate-dotnet-maui-apps-uikit-scene-lifecycle/

The lastest Maui 10 and 11 releases require Xcode 27.2

0 comments

Answer 3

Yes. The error is a toolchain mismatch: the build is using .NET for iOS 26.0.11017, which was validated for Xcode 26.0, while the Mac now has Xcode 27.0 selected.

The supported fixes are:

Install the Xcode version required by the error
- Install Xcode 26.0 alongside Xcode 27.0.
- Then select the required Xcode on the Mac with:
```
     xcode-select --switch <path-to-Xcode-26.0>
```
- This is the simplest supported path when the error explicitly names the required Xcode version.
Use a .NET for iOS workload version that supports Xcode 27.0
- Each .NET for iOS workload requires a specific Xcode version.
- The exact supported Xcode version for a workload is listed in the release notes.
- If support for Xcode 27.0 has been released, install the matching workload set version.
If Visual Studio is pointing to an old or removed Xcode path, reset Xcode selection on the Mac
- Delete these files if they exist:
  - ~/Library/Preferences/Xamarin/Settings.plist
  - ~/Library/Preferences/maui/Settings.plist
- Then either:
  - run xcode-select --switch ..., or
  - set DEVELOPER_DIR to the intended Xcode path.

Important details for this case:

The installed CLI workloads shown in dotnet workload list are 27.2.11039/11.0.100, but the error mentions 26.0.11017. That indicates Visual Studio is building with an older .NET for iOS toolchain than the one shown in the command-line output.
Updating macOS and Xcode alone can trigger this problem because newer Xcode versions often require matching newer workloads.
Using a different Xcode version than the one required may work in limited cases, but it is not supported.
As a temporary workaround only, the Xcode version check can be skipped by setting this in the project file:
```
  <ValidateXcodeVersion>false</ValidateXcodeVersion>
```
This is not a supported long-term fix.

For immediate debugging reliability, the lowest-risk option is to install Xcode 26.0 alongside Xcode 27.0 and switch to it when building this project.

References: