A Microsoft open-source framework for building native device applications spanning mobile, tablet, and desktop.
Hi @Sara Silva ,
Thank you for sharing the screenshots and for your patience throughout this investigation. However, based on the screenshots alone, the current Debug output does not contain enough information to determine the exact root cause of the issue.
Visual Studio provides built-in diagnostic logging that can capture detailed runtime information, binding failures, exceptions, and other relevant events. Reviewing these logs can help us accurately identify the root cause of the issue and determine the most appropriate resolution.
- Open Tools > Options.
- Set MSBuild project build output verbosity to Diagnostic.
- Open View > Output.
- Select Build in the Show output from list.
- Rebuild the project and run the iOS Simulator again.
- Review the complete Build and Debug output, especially any warnings or errors.
As an additional isolation test, temporarily disable:
Tools > Options > .NET MAUI > Apple > Remote Simulator to Windows
Then run the application again and verify whether the simulator opens directly on the Mac. This helps determine whether the issue is related to the Windows Remote Simulator or to the build/deployment process itself.
The diagnostic logs may provide additional details that are not visible in the screenshots alone. By reviewing the complete output, we can verify exactly where the process is failing, identify the underlying cause, and work toward the most appropriate resolution.
Microsoft documentation:
If this instruction is applicable to your situation, I would greatly appreciate it if you could follow the instruction here so others experiencing similar behavior can benefit from it as well.