Pair to Mac failed with the error “The Xcode license status couldn't be verified because Xcode has not been found...”

[v-Lily]

Description

Pair to Mac failed with the error as below:

The Xcode license status couldn't be verified because Xcode has not been found on the default location of the connected Mac. Having Xcode installed and functional is necessary in order to build and run iOS apps, so please check that Xcode is correctly installed and that the path specified under iOS Settings is correct.

Steps to Reproduce

1. Install the build from the VS PR CloudBuild: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=6784435&view=ms.vss-build-web.run-extensions-tab
2. Add a few feeds to your NuGet.config:

  <packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
    <add key="dotnet7" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7/nuget/v3/index.json" />
    <add key="dotnet7-internal" value="https://pkgs.dev.azure.com/dnceng/internal/_packaging/7.0.100-rc.2.22477.23-shipping/nuget/v3/index.json" />
    <add key="dotnet6" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json" />
    <add key="dotnet6-internal" value="https://pkgs.dev.azure.com/dnceng/internal/_packaging/6.0.402-servicing.22476.26-shipping/nuget/v3/index.json" />
  </packageSources>
  <packageSourceCredentials>
    <dotnet7-internal>
      <add key="Username" value="[email protected]" />
      <add key="ClearTextPassword" value="PLACEHOLDER_YOUR_PAT_HERE" />
    </dotnet7-internal>
    <dotnet6-internal>
      <add key="Username" value="[email protected]" />
      <add key="ClearTextPassword" value="PLACEHOLDER_YOUR_PAT_HERE" />
    </dotnet6-internal>
  </packageSourceCredentials>

3. If you want to pair with the mac build agent, follow these iinstructions: https://devdiv.visualstudio.com/DevDiv/_wiki/wikis/DevDiv.wiki/30321/Private-dotnet-SDK-and-workloads-Manual-Installation
4. On the Windows machine, create a new Blazor Hybrid project on the command line using the following: dotnet new maui-blazor -o iOSWindowsProject
5. Open the iOSWindowsProject solution with Visual Studio.
6. Select the "Pair to Mac" option in the Visual Studio toolbar.
7. Select the mac OS device that is connected to the network and press "Connect".
8. In the next window, enter the username and password for the user account on the macOS machine.
9. Connect the machine.

Actual Pair to mac failed. After click “ok”, the waring will change Continue click “ok”, it will show the error

Note We try to the bellow resolutions, But it still doesn’t work.

1. Reinstall Xcode
2. Change IOS setting to give a Xcode path

3. Try some commands on Mac, e.g:

 sudo xcode-select –reset
 sudo xcodebuild -license
 sudo xcode-select -s /Applications/Xcode.app

Link to public reproduction project repository

No

Version with bug

Unknown/Other (please specify)

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

Windows SDK 7.0.100-rc.2.22477.23

Did you find any workaround?

No

Relevant log output

The Xcode license status couldn't be verified because Xcode has not been found on the default location of the connected Mac. Having Xcode installed and functional is necessary in order to build and run iOS apps, so please check that Xcode is correctly installed and that the path specified under iOS Settings is correct.


The Xcode tools validation couldn't be performed because IDB has not been started successfully on the paired Mac, which is necessary in order to read the iOS Remote Settings. Having a non functional paired Mac or the Xcode tools not updated could cause unwanted behaviors. Please check the logs to see what happened with IDB initialization on the paired Mac.

The connection to the Mac has been lost in the middle of the process. Please try to connect again

[kfrancis]

Seeing the same.

[ghost]

Thanks for the issue report @v-Lily! This issue appears to be a problem with Visual Studio, so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS.

If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.

1. Go to the VS feedback tool to report the issue
2. Close this bug, and consider adding a link to the VS Feedback issue so that others can follow its activity there.

This issue will be automatically closed in 3 days if there are no further comments.

[v-Lily]

@PureWeen @TanayParikh @kfrancis This issue does not reproduce after installing the latest Dev17.4 VS and maui version (The detailed configuration info see here), I will continue to track this issue.

[TanayParikh]

Should we close out this issue in that case?

[ghost]

Hi @v-Lily. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[v-Lily]

@TanayParikh @PureWeen I'm not sure if this is an unstable bug, I will continue to track this issue for a week. If this issue doesn't reproduce I will close it.

[WebGoose]

I am getting this issue as well after I updated to the latest VS Preview yesterday.

[ghost]

This issue is being closed due to inactivity. If this issue is still affecting you, please follow the steps above to use the VS Feedback Tool to report the issue.

[Saulawa]

I updated to the latest version of Visual studio both on mac and windows and I still get the same problem

[TanayParikh]

@v-Lily was this reported to VS? If so, can you please provide the VS issue here for tracking.

[v-Lily]

@TanayParikh We haven't met this issue for two weeks, and there is no environment to reproduce the issue reported to VS. I will continue to track this issue.

[TanayParikh]

I updated to the latest version of Visual studio both on mac and windows and I still get the same problem

@Saulawa can you please report this to VS via the Report a Problem feature in VS. This assures the appropriate data is captured and routed to the right team.

[JORGEGO]

Same problem!!

[ghost]

Hello lovely human, thank you for your comment on this issue. Because this issue has been closed for a period of time, please strongly consider opening a new issue linking to this issue instead to ensure better visibility of your comment. Thank you!

[JORGEGO]

It seems fixed if you execute sudo xcode-select -r from Mac Terminal

[HobDev]

I am facing this issue in Visual Studio 17.4.3

[ghost]

Hello lovely human, thank you for your comment on this issue. Because this issue has been closed for a period of time, please strongly consider opening a new issue linking to this issue instead to ensure better visibility of your comment. Thank you!

[jingliancui]

I met same problem, workaround is downgrade to xcode14.1

[HobDev]

@jingliancui I reported this bug on Visual Stuido Developer Community. The solution could help you.