Share via

Could not install workload 'ios'. Error installing the manifest "microsoft.net.sdk.ios" in version 26.2.10233

Kim Strasser 2,536 Reputation points
2026-04-29T09:52:38.05+00:00

I have updated Visual Studio Community 2026 to version 18.5.2 today and now pairing to my MacBook Air is no more working:

Could not install workload 'ios'. Error installing the manifest "microsoft.net.sdk.ios" in version 26.2.10233

And it displays that it cannot load from https://api.nuget.org/v3/index.json.

Then I have used the command dotnet workload update in my project and tried again to pair but it still doesn´t work. I use Xcode version 26.3 on my MacBook Air.

Developer technologies | .NET | .NET MAUI
0 comments No comments

Answer accepted by question author

  1. Varsha Dundigalla(INFOSYS LIMITED) 4,945 Reputation points Microsoft External Staff
    2026-04-29T12:35:58.5033333+00:00

    Thank you for reaching out.

    This error is happening because Visual Studio is not able to download the iOS workload from NuGet.

    The message “cannot load https://api.nuget.org/v3/index.json” means the machine is not able to reach NuGet properly. Because of that, the iOS workload manifest (microsoft.net.sdk.ios) cannot be installed, so pairing to Mac fails.

    This is usually not a problem with your project, but with connectivity or environment setup.

    First, please check if the NuGet URL opens in your browser. If it does not load, then it is a network issue (proxy, firewall, VPN, etc.). Even if it opens in browser, NuGet inside .NET can still fail due to proxy or TLS differences.

    You can try the following steps:

    • Clear NuGet cache
        dotnet nuget locals all --clear
      
    • Clean and reinstall workloads
        dotnet workload clean 
        dotnet workload update 
        dotnet workload install ios
      
    • Try from a different network (for example, mobile hotspot) to rule out firewall or proxy blocking

    If the issue continues, check NuGet source settings and temporarily switch to the v2 feed (https://www.nuget.org/api/v2/) as a workaround when v3 API is not reachable

    Also, after fixing the NuGet issue, make sure the Xcode version on the Mac matches what the installed iOS workload expects. If the versions do not match, pairing will still fail even if the workload installs correctly.

    Please let us know if you require any further assistance, we’re happy to help. If you found this information useful, kindly mark this as "Accept Answer". So that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    2 people found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Q&A Assist
    2026-04-29T09:53:07.52+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error indicates that the updated Visual Studio / .NET SDK is trying to install or update the iOS workload to a specific manifest version (26.2.10233), but it cannot download the manifest from NuGet. Separately, pairing can also fail if the installed Xcode version does not match what the installed .NET for iOS workload expects.

    Address both issues in this order:

    1. Check Xcode version compatibility
      • Each .NET for iOS / MAUI iOS workload requires a specific Xcode version. If the installed workload expects a different Xcode than 26.3, pairing and builds can fail.
      • The error message that appears when Xcode is mismatched is similar to:

        This version of Microsoft.iOS requires the iOS 18.4 SDK (shipped with Xcode 16.3). The current version of Xcode is 16.2. Either install Xcode 16.3, or use a different version of Microsoft.iOS.

      • Check the .NET for iOS / MAUI release notes for the Visual Studio 18.5.x version in use and verify which Xcode version is required. If the required Xcode version is not 26.3, either:
        • Install the required Xcode version on the Mac, or
        • Install an older .NET for iOS / MAUI workload version that matches Xcode 26.3.
    2. Ensure the iOS workload is installed for the current .NET SDK
      • The error about installing the manifest microsoft.net.sdk.ios means the iOS workload is not correctly installed for the .NET SDK that Visual Studio 2026 is using.
      • From a Developer Command Prompt that uses the same .NET SDK as Visual Studio 2026, run:
             dotnet workload install ios
        
      • If the project targets a MAUI iOS workload, also ensure the MAUI workloads are installed (for example maui-ios, maui-mobile, etc., depending on the project). The general pattern for missing workloads is:

        NETSDK1147: To build this project, the following workloads must be installed: <workload ID> and then:

             dotnet workload install <workload ID>
        
    3. Avoid pulling a mismatched manifest version
      • dotnet workload update without version pinning can pull newer manifests that expect newer Xcode or other dependencies.
      • To keep workloads aligned with a specific workload-set version that matches Visual Studio and Xcode, use a pinned install:
             dotnet workload install maui-ios --version <workload-set-version>
        
        where <workload-set-version> is the workload-set version that corresponds to the Visual Studio 2026 build in use.
      • After running a pinned install once, subsequent dotnet workload install commands (for example for ios or other workloads) will use the same workload-set version.
    4. Retry pairing after workloads and Xcode are aligned
      • Once the iOS / MAUI workloads are successfully installed and the Xcode version matches what the workload requires, restart Visual Studio 2026 and retry pairing to the Mac.
      • If pairing still fails, verify that the Mac has the same .NET for iOS / MAUI workload versions installed (if using local builds on the Mac) and that Xcode is correctly selected and opened at least once.

    If the manifest download from https://api.nuget.org/v3/index.json continues to fail, the remaining causes are typically network-related (firewall/proxy/SSL inspection blocking NuGet) and must be resolved so that dotnet workload install can reach NuGet to download the workload manifests.


    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.