Debugger can't launch iOS app on the iPhone device

AdrianKnightAdrianKnight USMember ✭✭✭✭

Visual Studio starts running the debugger, but this is the error I'm getting in the console:

Launching 'App26iOS' on 'x's iPhone'...
Launch failed. The app 'App26iOS' could not be launched on 'x's iPhone'. Please check the logs for more details.

The app doesn't start running on the iPhone. If I tap on the app icon, then VS debugger will continue and write a bunch of stuff to the console.

When the error says to check the logs, where do I look for the logs? Where are they located?

This started happening after I updated to 2.2.0.23-pre4.

Answers

  • GeraldVersluisGeraldVersluis NLUniversity ✭✭✭✭

    Where does this message come from?
    Check either the build or Xamarin logs maybe for more info.
    To get logs of your phone you should check XCode.

  • StefanAStefanA NLMember
    edited April 2016

    In the output window select the logs for Xamarin. There you will see the actual error.

    Is the phone unlocked when you deploy?

  • AdrianKnightAdrianKnight USMember ✭✭✭✭

    @GeraldVersluis The message is in VS 2015's console. I just created a new project and started debugging.

    Launching 'App3iOS' on 'x's iPhone'...
    Launch succeeded. The app  'App3iOS' has been successfully launched on 'x's iPhone'.
    

    This time it says launch succeeded, but the app doesn't start running on the device unless I tap on the app icon. @StefanA yes the phone is unlocked upon app deploy.

  • AdrianKnightAdrianKnight USMember ✭✭✭✭

    In the Xamarin log window, I don't see anything wrong.

    Starting Broker 4.1.0.313 in port 57780...
    SSH Connection established with the Mac 192.168.0.104:57780
    Starting agents on Mac 192.168.0.104 (192.168.0.104)
    Starting Agent IDB 4.1.0.313...
    Agent IDB 4.1.0.313 is running
    Starting Agent Build 4.1.0.313...
    Agent Build 4.1.0.313 is running
    Starting Agent Designer 4.1.0.313...
    Agent Designer 4.1.0.313 is running
    Connected to the Mac 192.168.0.104 (192.168.0.104) with Full support.
    
  • AdrianKnightAdrianKnight USMember ✭✭✭✭

    @GeraldVersluis @StefanA

    Here are some of the warnings I see with respect to linker optimization. I'm not sure if this could be the cause.

  • AlanAndersonAlanAnderson USUniversity ✭✭

    I'm having a similar problem, I updated the Beta channel to pick up some of the new features, now I can debug the app perfectly using the iOS simulator, but when I try to debug on my iPhone (previously worked), now I get a message:
    Launch failed. The app 'xxxiOS' could not be launched on 'Alan's iPhone 6'. Please check the logs for more details. The log has a bunch of exceptions starting with:

    Xamarin.Messaging.Client.MessagingClient Error: 0 : [2016-05-01 03:28:09.7629] An error occured on the receiver while executing a post for topic xvs/idb/4.1.0.462/launch-app and client vs6524AANDE
    Xamarin.Messaging.Exceptions.MessagingRemoteException: An error occured on client IDB410462 while executing a reply for topic xvs/idb/4.1.0.462/launch-app ---> Xamarin.Messaging.Exceptions.MonotouchException: warning HE0041: Error while processing device notifications: NotificationCallback with unknown message: 5

    Is anyone else having this problem? if I manually run the app on the device (even deleted it) and it seems to work ok, just can't run from the debugger in Visual Studio. I thought I was having a provisioning profile issue, but now I don't think that is the problem.

    Alan

  • JohnHardmanJohnHardman GBUniversity mod

    I've been having a similar problem since updating to 2.2.0.39 . It doesn't happen every time. I'm not 100% sure, but it feels like it happens after switching from one physical iOS device to another (I use an iPhone and an iPad), and a power-cycle of the device and/or a VS re-start solves it until the next time. Not ideal.

  • SteveHatchSteveHatch USMember ✭✭

    I am having the same problem since updating on 6/8/16. My iPhone worked perfectly before and now I get this same error. I can deploy to my iPad however. I wish Xamarin would take some of these issues serious as they seriously hamper developers. My app needs to be deployed to work, I cannot use the simulator. When I google "xamarin ios failed to launch on device" and get tons of hit with several people asking the same questions, it's a bug Xamarin, don't sweep it under the rug.

  • DanKloDanKlo USUniversity ✭✭

    Hi there, had the same issue and I solved it by starting VS in CMD with ResetSettings command: Devenv /ResetSettings General

  • SteveHatchSteveHatch USMember ✭✭

    I tried resetting the settings as suggested, I get exactly the same results.

    This iPhone worked perfectly until the latest Xamarin update. The logs give me no indication what is wrong, they just contain an exception to the effect that the debugger cannot start.

    XAMARIN PLEASE HELP! My Development is halted, I cannot develop this app with a simulator and I don't have several iPhone's setting around to use until each mysteriously stops working.

  • SteveHatchSteveHatch USMember ✭✭

    Additional info. I can deploy and debug on this same iPhone from xcode.

  • SteveHatchSteveHatch USMember ✭✭

    More additional info: I was able to fix the problem by clearing all contents on my phone and then restoring. This is just a work around, Xamarin still needs to figure out why this happens. There are far too many people experiencing this to continue ignoring it.

  • TimothyLeeRussellTimothyLeeRussell USMember ✭✭

    Same problem here. Deploys the app but can't launch debugging. It can be started manually on the iOS device.

    iOS device logs show my app crashing because "Thread 7: Debugger agent" crashed.

    and in the Xamarin logs:
    Xamarin.Messaging.Client.MessagingClient Error: 0 : [2016-06-18 16:52:22.4762] An error occured on the receiver while executing a post for topic xvs/idb/4.2.0.21/launch-app and client vs8924timot
    Xamarin.Messaging.Exceptions.MessagingRemoteException: An error occured on client IDB42021 while executing a reply for topic xvs/idb/4.2.0.21/launch-app --->
    Xamarin.Messaging.Exceptions.MonotouchException: warning HE0041: Error while processing device notifications: NotificationCallback with unknown message: 5
    at Xamarin.Messaging.IDB.MTouch+d__6.MoveNext () <0x67def20 + 0x007bb> in :0

  • JGoldbergerJGoldberger USMember, Forum Administrator, Xamarin Team, University Xamurai
  • JGoldbergerJGoldberger USMember, Forum Administrator, Xamarin Team, University Xamurai
  • HectorMenesesHectorMeneses USMember ✭✭

    Is there are way of getting notified when this bug gets resolved?
    Thanks,
    Hector

  • AlanAndersonAlanAnderson USUniversity ✭✭

    I reinstalled Visual Studio and everything was working after this original post on May 1st, just updated to the latest stable Xamarin for Visual Studio and it is BACK. I can debug using a iOSSimulator, but physical devices don't work yet again. I don't know how people are supposed to write apps having these setup issues all the time. Does anyone have a solution? I hate to re-install Visual Studio again - but I'm afraid that is the fix, just like last time.

    Thanks for any assistance.

    Same messages as before:
    Launching 'BuilderAppiOS' on 'Alan's iPhone 6'...
    The app has been terminated.
    Launch failed. The app 'BuilderAppiOS' could not be launched on 'Alan's iPhone 6'. Please check the logs for more details.

    Log contains:
    Xamarin.Messaging.Client.MessagingClient Error: 0 : [2016-06-29 00:12:15.5143] An error occured on the receiver while executing a post for topic xvs/idb/4.1.1.3/launch-app and client vs4868AANDE
    Xamarin.Messaging.Exceptions.MessagingRemoteException: An error occured on client IDB4113 while executing a reply for topic xvs/idb/4.1.1.3/launch-app ---> Xamarin.Messaging.Exceptions.MonotouchException: warning HE0041: Error while processing device notifications: NotificationCallback with unknown message: 5

    at Xamarin.Messaging.IDB.MTouch+d__6.MoveNext () <0x74b9220 + 0x007e3> in :0
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in :0
    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x1bd48b0 + 0x0001f> 25494 in <filename unknown>:0 at Xamarin.Messaging.IDB.MTouch+<DeployAsync>d__4.MoveNext () <0x76c2938 + 0x0032f> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x1bd48b0 + 0x0001f> 25494 in :0
    at Xamarin.Messaging.IDB.Handlers.LaunchAppMessageHandler+d__17.MoveNext () <0x76c2198 + 0x0021b> in :0
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in :0
    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x1bd48b0 + 0x0001f> 25494 in <filename unknown>:0 at Xamarin.Messaging.IDB.Handlers.LaunchAppMessageHandler+<ExecuteOnPhysicalDeviceWithoutAssetsAsync>d__16.MoveNext () <0x76c0bf8 + 0x001db> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x1bd4ad0 + 0x0001f> 25501 in :0
    at Xamarin.Messaging.IDB.Handlers.LaunchAppMessageHandler+d__14.MoveNext () <0x76c0000 + 0x004b7> in :0
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in :0
    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x1bd4ad0 + 0x0001f> 25501 in <filename unknown>:0 at Xamarin.Messaging.IDB.Handlers.LaunchAppMessageHandler+<ExecuteAsync>d__12.MoveNext () <0x761f588 + 0x0039f> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter1[TResult].GetResult () <0x18a7bc0 + 0x00024> in :0
    at Xamarin.Messaging.Client.RequestHandler2+<HandleAsync>d__5[TMessage,TResult].MoveNext () <0x74b36a0 + 0x003d7> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x18a8040 + 0x00024> in :0
    at Xamarin.Messaging.Client.MessageHandlerManager+<>c__DisplayClass17_02+<<RegisterHandlerAsync>b__1>d[TMessage,TResult].MoveNext () <0x74b2ce0 + 0x002bb> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x18a8040 + 0x00024> in :0
    at Xamarin.Messaging.Client.MessagingClient+d__342[TRequest,TResponse].MoveNext () <0x74b1d68 + 0x00383> in <filename unknown>:0 --- End of inner exception stack trace --- at Xamarin.Messaging.Client.MessagingClient.<PostAsync>d__232.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Xamarin.Messaging.Client.MessagingClient.d__222.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Xamarin.Messaging.Client.MessagingClient.<PostAsync>d__262.MoveNext()
    Xamarin.VisualStudio.IOS.IdbClient Error: 0 : [2016-06-29 00:12:18.8800] Launch failed. The app 'BuilderAppiOS' could not be launched on 'Alan's iPhone 6'. Please check the logs for more details.
    Xamarin.Messaging.Exceptions.MonotouchException: warning HE0041: Error while processing device notifications: NotificationCallback with unknown message: 5

    at Xamarin.Messaging.IDB.MTouch+d__6.MoveNext () <0x74b9220 + 0x007e3> in :0
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in :0
    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x1bd48b0 + 0x0001f> 25494 in <filename unknown>:0 at Xamarin.Messaging.IDB.MTouch+<DeployAsync>d__4.MoveNext () <0x76c2938 + 0x0032f> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x1bd48b0 + 0x0001f> 25494 in :0
    at Xamarin.Messaging.IDB.Handlers.LaunchAppMessageHandler+d__17.MoveNext () <0x76c2198 + 0x0021b> in :0
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in :0
    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x1bd48b0 + 0x0001f> 25494 in <filename unknown>:0 at Xamarin.Messaging.IDB.Handlers.LaunchAppMessageHandler+<ExecuteOnPhysicalDeviceWithoutAssetsAsync>d__16.MoveNext () <0x76c0bf8 + 0x001db> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x1bd4ad0 + 0x0001f> 25501 in :0
    at Xamarin.Messaging.IDB.Handlers.LaunchAppMessageHandler+d__14.MoveNext () <0x76c0000 + 0x004b7> in :0
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in :0
    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in :0
    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x1bd4ad0 + 0x0001f> 25501 in <filename unknown>:0 at Xamarin.Messaging.IDB.Handlers.LaunchAppMessageHandler+<ExecuteAsync>d__12.MoveNext () <0x761f588 + 0x0039f> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter1[TResult].GetResult () <0x18a7bc0 + 0x00024> in :0
    at Xamarin.Messaging.Client.RequestHandler2+<HandleAsync>d__5[TMessage,TResult].MoveNext () <0x74b36a0 + 0x003d7> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x18a8040 + 0x00024> in :0
    at Xamarin.Messaging.Client.MessageHandlerManager+<>c__DisplayClass17_02+<<RegisterHandlerAsync>b__1>d[TMessage,TResult].MoveNext () <0x74b2ce0 + 0x002bb> in <filename unknown>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x18aa010 + 0x00035> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x18a7830 + 0x000b7> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x18a7790 + 0x00087> in <filename unknown>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x18a7740 + 0x0003f> in <filename unknown>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () <0x18a8040 + 0x00024> in :0
    at Xamarin.Messaging.Client.MessagingClient+d__34`2[TRequest,TResponse].MoveNext () <0x74b1d68 + 0x00383> in :0

  • AdrianKnightAdrianKnight USMember ✭✭✭✭

    I updated my IDE to VS 2013 Update 3 and started getting this very often. Restarting VS doesn't seem to help.

  • TimothyLeeRussellTimothyLeeRussell USMember ✭✭

    As of the latest beta, 07/29/2016, this is still an issue for me.

    All Mac and Win10 OS and VS2015 updates are current.

    Xamarin 4.1.2.18 (fcbe082)
    Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
    Xamarin Inspector Support 0.3.2.3 (1b526e6)
    Adds support for inspecting Xamarin and WPF apps.
    Xamarin.Android 6.1.2.21 (1cf254d)
    Visual Studio extension to enable development for Xamarin.Android.
    Xamarin.iOS 9.8.2.22 (f37444a)
    Visual Studio extension to enable development for Xamarin.iOS.

    The bug for it is marked as verified / fixed but I am unfortunately, not one of the lucky ones.

    https://bugzilla.xamarin.com/show_bug.cgi?id=41655

    I'm not totally down, since it does deploy the app successfully and I can run it and test it manually...and can debug on the Android side.

    Still, I'm looking forward to being able to debug on iOS again, since unfortunately, I'm not a good enough software engineer to write code (that doesn't suck) without the debugger.

    Any ideas?

    Thanks!
    Timothy

  • MattJackMattJack FRMember ✭✭

    I'm facing the same problem.
    Please Xamarin find a solution; at least give some workaround.
    Thanks

  • Have the same problem. If someone knows how to fix or any workaround, S.O.S.!

  • JohnHardmanJohnHardman GBUniversity mod

    I was getting the failed to launch pretty much every time. One of the multiple updates I have installed recently seems to have resolved that. However, now I quite often end up with the app launched, but the VS2015 Update 3 IDE is not in control of debugging, with breakpoints not activating and nothing appearing in the VS2015 Output Window.

  • JohnWilkinsJohnWilkins GBMember ✭✭
    edited August 2016

    I have VS2015 with all the latest updates, Xamarin.iOS 9.8.2.22, Xamarin 4.1.2.18 - essentially every thing to the latest stable builds.

    I have the same problem, every time. No matter what I try - restarting devices, rebooting - I get the same error. I am unable to debug on my iPhone. I can run within a simulator.

    This is a critical problem for me at the moment.

    Clearly the associated bug is not fixed - not for me and plenty of others.

    Any workarounds? Any fix imminent?

  • JohnWilkinsJohnWilkins GBMember ✭✭

    Original bug 41655 is showing as verified fixed, as reported by @TimothyLeeRussell so I've opened a new related bug.

    https://bugzilla.xamarin.com/show_bug.cgi?id=43239

  • I would suggest using Xamarin studio on Mac for debugging the app on a device. In this case it is possible to debug, from my experience.

  • FredrikHaglundFredrikHaglund SEUniversity, Developer Group Leader ✭✭

    This is probably not a Xamarin.Forms problem.

    I also got "Launch failed." for real devices after upgrading Xamarin Visual Studio from 4.0.4 to current stable 4.1.2. I tried 4.1 and 4.1.1 with same problem.

    I'm able to use Xamarin Studio on Mac for debugging as a workaround until it is fixed.

    Xamarin found a resolution to this and there is a patch available to test if it resolves your issue.

    See: https://bugzilla.xamarin.com/show_bug.cgi?id=43239#c14

    The patch worked for me so I expect this to be fixed in an upcoming release and I keep my fingers crossed I can get a hotfix through support before that to be able to stay in Visual Studio when I debug.

  • JohnWilkinsJohnWilkins GBMember ✭✭

    The bug I raised to deal with this:

    https://bugzilla.xamarin.com/show_bug.cgi?id=43239

    now has a solution. It's had three independent verifications, including mine. I'm now able to debug normally on devices.

  • JamesWierzbaJamesWierzba USMember
    edited January 2017

    I'm experiencing this issue and my Xamarin version is greater than the one reported to have the fix (in the bug report linked above)

    Launching 'App.iOS' on 'iPhone 6 iOS 10.2'...
    Launch failed. The app 'App.iOS' could not be launched on 'iPhone 6 iOS 10.2'. Error: The post for client vs4064jwier on topic xvs/idb/4.2.1.64/launch-app has been cancelled. Please check the logs for more details.
    The app has been terminated.

  • CarLoOSXCarLoOSX USMember ✭✭

    I was having this problem :

    error HE0042: Could not launch the app on the device 'iOS 10.3 (14E8301) - iPhone 7': The request to open failed.

    The solution was:

    Open simulator -- > click on the top menu Simulator --> click on **Reset Content and Settings.... **

    Once the process has finished, you can try again to deploy, it should work again.

    Sorry about my english ! :D

  • BhaurajBiradar.9064BhaurajBiradar.9064 USMember ✭✭✭

    Hi, It's an connectivity problem between Windows VS with Mac Mini and sometime remote Mac Mini moves to sleep mode.

  • LyndonHugheyLyndonHughey USUniversity ✭✭✭

    I'm also noticing this error and its seems to be caused by a disconnect between my mac and Windows VS in a VM.

  • Sushil_KumarSushil_Kumar Member ✭✭

    Hi

    Please help me, I am new in Xamarin.Forms

    I am getting below errors in iOS in Xamarin.Forms

    Failed to Stop app: An error occured on client IDB412369 while executing a reply for topic xvs/idb/4.12.3.69/stop-app.
    The app has been terminated.

    Thanks

  • JohnHJohnH GBMember ✭✭✭✭✭

    @Sushil_Kumar said:
    Hi

    Please help me, I am new in Xamarin.Forms

    I am getting below errors in iOS in Xamarin.Forms

    Failed to Stop app: An error occured on client IDB412369 while executing a reply for topic xvs/idb/4.12.3.69/stop-app.
    The app has been terminated.

    Thanks

    I suggest starting your own thread, this does not appear to be related to the original post from 2 years ago.

Sign In or Register to comment.