Visual Studio 2022 not deploying Maui app to iPhone Simulator

[pabloquesadaglobant]

Hello!
My Visual Studio 2022 (in my Windows machine) is already paired to a network-accesible Mac machine. I'm selecting an iOS simulator (I tried them all) from the list and click the Play button (for starting debugging). It takes some seconds and I see the status message in Visual Studio saying "Deploy succeeded"; also the Output window says "Deploy started at...". BUT the simulator never appear. In fact, the Run button in Visual Studio become green again (saying nothing is running). I also can see the remote Mac computer is not running the app at all. There is no error message in any place saying something went wrong.

Something very important: until 3 or 4 days ago, I was able to execute the app in the iPhone simulator with no problems. I'm able to run the app in Android emulator and physical devices.

Any clue in how to resolve this issue? Thanks in advance!

[JohnHDev]

Could try to clean all, reboot both Mac and windows, delete bin and obj directories etc.

[pabloquesadaglobant]

Thank you @JohnHDev, I forgot to mention in my original post that I actually tried clean and reboot of both computers. But I didn't try deleting the folders... and that worked! I appreciate the help!

[anupniit]

This is happening to me as well, I tried both cleaning and deleting the bin and obj folder but still not working.

[CHIPSNetwork]

Same problem in 17.8.358.6298 with a new / clean MAUI project. Is there any way to troubleshoot this, or is it just broken until a future release?

[najak3d]

Happening here now, on latest versions of XCode (15.4), VStudio (17.9.7), everything -- and happens exactly as reported by the OP (says it deploys and starts, but no Simulator shows).

This worked a few days ago, and just stopped working, not sure why, and can't seem to fix it. Tried deleting bin/obj with Clean Solution -- makes no difference, still fails.

[eqmarcin]

@najak3d
Happened to me today - XCode 15.2 & VS 17.9.7.
Deleting bin/obj with Clean Solution -- makes no difference, still fails as above.

I opened Project #2 and emulator and app started OK.
Closed Project #2 and re-opened Project #1 and now it works?!

I noticed that earlier I was not able to see any Signing Identities under project Properties > iOS > Bundle Signing.
Now I see them all.
Looks like some connectivity issue between VS and XCode.

[DevelopmentDan]

Don't forget to switch back to "Automatic Provisioning" under iOS Bundle Signing, when switching back to Debug from Release.

[mackayn]

This is happening constantly now in VS2022 17.10.1 (Win11 Pro x64) onto a macBook Pro M2 with XCode 15.2, 15.3 or 15.4, you cannot attach a debugger or even do a deploy although SIM works if you force in the hacks thanks to AppCenter. Delete obj & bin makes no difference

`
, _iOSRuntimeIdentifier: ios-arm64, IsHotRestartBuild: False, MessagingVersion: 17.2.8053, _DotNetRootRemoteDirectory: /Users/admin\Library\Caches\Xamarin\XMA\SDKs\dotnet/, ServerSshPort: 22, ServerTcpPort: 51410, ServerUser: admin, ContinueOnDisconnected: False, ServerAddress: 192.168.1.99: 05/30/2024 12:10:27Z
DateTime=2024-05-30T12:10:27.1188427Z: 05/30/2024 12:10:27Z
Xamarin.Messaging.Client.MessagingClient Error: 0 : An error occurred on the receiver while executing a post for topic xvs/idb/deploy-app and client vs29632norma
Xamarin.Messaging.Exceptions.MessagingRemoteException: An error occurred on client IDB17100110 while executing a reply for topic xvs/idb/deploy-app ---> Xamarin.Messaging.Exceptions.MonotouchException: error MT1045: Failed to execute 'devicectl': 'devicectl -j /var/folders/np/w_4cckh5337bhvr8s9f3bh0r0000gn/T/tmpo5lRJj.tmp device install app --device "X iPhone" /Users/admin/Library/Caches/Xamarin/mtbs/builds/Blah.Primary/955650db5534ea6ec34e155df6171c03d8cfec9692a6f9144918bdaa1a30cd00/bin/Debug/net8.0-ios/ios-arm64/device-builds/iphone13.2-17.4.1/Blah.Primary.app' returned the exit code 1.

at Xamarin.Messaging.IDB.MTouch.RunAsync (System.Collections.Generic.IEnumerable1[T] parameters, System.Threading.CancellationToken cancellationToken, System.Func2[T,TResult] exitCondition, Xamarin.Messaging.IDB.MTouchProcessType processType, System.Func2[T,TResult] reportProgressAsync, System.Func2[T,TResult] handleOutputAsync) [0x00302] in <4b80af867f434a68adcb38c5f964e5c7>:0
at Xamarin.Messaging.IDB.MTouch.DeployAsync (Xamarin.Messaging.IDB.Contracts.AppInfo appInfo, Xamarin.Messaging.IDB.Contracts.AppleDevice device, System.Boolean debugging, System.Func2[T,TResult] reportProgressAsync, System.Boolean forceDeploy) [0x0039d] in <4b80af867f434a68adcb38c5f964e5c7>:0 at Xamarin.Messaging.IDB.MTouch.DeployAsync (Xamarin.Messaging.IDB.Contracts.AppInfo appInfo, Xamarin.Messaging.IDB.Contracts.AppleDevice device, System.Boolean debugging, System.Func2[T,TResult] reportProgressAsync, System.Boolean forceDeploy) [0x0054e] in <4b80af867f434a68adcb38c5f964e5c7>:0
at Xamarin.Messaging.IDB.DeployAppMessageHandler.ExecuteAsync (Xamarin.Messaging.IDB.Contracts.DeployAppMessage message) [0x0009a] in <4b80af867f434a68adcb38c5f964e5c7>:0
at Xamarin.Messaging.Client.RequestHandler2[TMessage,TResult].HandleAsync (TMessage message) [0x0010e] in <1c51cfa478c8448a80a7bde38e0ad475>:0 at Xamarin.Messaging.Client.MessageHandlerManager+<>c__DisplayClass16_12[TMessage,TResult].b__2 () [0x00084] in <1c51cfa478c8448a80a7bde38e0ad475>:0
at Xamarin.Messaging.Client.MessagingClient.ReplyAsync[TRequest,TResponse] (Xamarin.Messaging.Client.IRequest1[T] request, Xamarin.Messaging.MessagePriority priority, System.Func1[TResult] replyFunctionAsync) [0x000c5] in <1c51cfa478c8448a80a7bde38e0ad475>:0
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Xamarin.Messaging.Client.ApplicationMessageExtensions.<>c__DisplayClass10_01.<OfResponse>b__1(MqttApplicationMessage m) in D:\a\_work\1\s\src\Xamarin.Messaging.Client\Extensions\ApplicationMessageExtensions.cs:line 194 at System.Reactive.Linq.ObservableImpl.Select2.Selector._.OnNext(TSource value)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Xamarin.Messaging.Client.MessagingClient.d__21`2.MoveNext() in D:\a_work\1\s\src\Xamarin.Messaging.Client\MessagingClient.cs:line 190: 05/30/2024 12:10:31Z
DateTime=2024-05-30T12:10:31.0528089Z: 05/30/2024 12:10:31Z
Xamarin.Messaging.Ssh.MessagingClientPro Warning: 0 : An error occurred while executing the operation. The host connection is active and running so no retries will be attempted.: 05/30/2024 12:10:31Z
DateTime=2024-05-30T12:10:31.0568091Z: 05/30/2024 12:10:31Z

`

[janvans]

I had the same issue - after doing a deploy to TestFlight I was not able to run the app in debug mode on a simulator again - everything seemed fine and it was deployed "successfully", but the simulator did not open, and even after opening the simulator manually, the app was not installed there. Although I've switched back from Manual to Automatic provisioning, I found the following PropertyGroup in the project file (Edit Project File) :

< PropertyGroup Condition="'$(TargetFramework)'=='net8.0-ios'">
     < ProvisioningType>manual< /ProvisioningType>
     < CodesignKey>iPhone Distribution: XXXXXXX)< /CodesignKey>
     < CodesignProvision>YYYYYYY< /CodesignProvision>
< /PropertyGroup>

I deleted this whole code block, saved and re-selected Automatic Provisioning using the visual project file editor, and everything worked as expected.
(Visual Studio v17.10.3 XCode v15.2)