locked
iOS - Visual Studio Locks up on "Launching Application for debugging" RRS feed

  • Question

  • User62427 posted

    I am trying to deploy and debug an iOS app on my iPad via a Mac Mini and "Xamarin Build Host".

    The app gets deployed but no breakpoints fire and Visual Studio either hangs or shutsdown. Where do I start debugging this issue?

    Thursday, December 18, 2014 5:23 PM

All replies

  • User62427 posted

    As well as it locking up at "Launching application". I currently have it locking up simply after a successful build.

    I am running

    Dell Laptop Mac Mini Small LAN with just me on it

    I can see issues in the Xamarin Build Host log but I do not know where to start to fix them. Can I get some help with this.

    Thursday, December 18, 2014 6:48 PM
  • User75831 posted

    I am having the a similar problem where I try to launch my application in debug mode. It literally goes through this output

    Launching Application for debugging... Stopping debugger... Debugging session ended. Launching Application for debugging...

    And then the application launches with the debugger left behind. My Console.WriteLine statements work and are visible but breakpoints are not hit. Does anyone know if there's an issue or resolution to attach the debugger? The debugger attached on my Android and WP.

    Tuesday, January 13, 2015 4:38 PM
  • User26457 posted

    Did anyone get this to stop? I started having the problem today after the 3.9.x most recent Xamarin update.

    Tuesday, January 13, 2015 6:05 PM
  • User52000 posted

    Yep, I get this as well. Here's what I got:

    Visual Studio 2013, Update 4

    Windows 8.1 Enterprise

    Parallels Desktop, Build 9.0.24251 (Revision 1052177; Thursday, August 28, 2014)

    mtouch 8.6.0.51 (dfb682f)

    Tuesday, January 13, 2015 10:09 PM
  • User27993 posted

    This has started happening for me too since updating to Xamarin.iOS 8.6, the app will deploy successfully, but visual studio will hang with "Launching Application for debugging..."

    It would be good to have a fix for this soon, VS support is the entire reason we are on a business subscription.

    Tuesday, January 13, 2015 11:42 PM
  • User75198 posted

    This has started occurring for me too after updating to Xamarin 3.9 yesterday. Visual Studio 2013 hangs on "Launching Application for Debugging..." and then VS locks up. After several minutes I receive this error in Error List Window:

    Error 3 There was an unhandled exception trying to deploy and run your application. System.AggregateException: One or more errors occurred. ---> System.Runtime.InteropServices.COMException: Solution unavailable. at EnvDTE.Project.getUniqueName() at Xamarin.VisualStudio.ProjectInterfaceConverters.ToHierarchy(Project project) at Xamarin.VisualStudio.IOS.Utilities.Helpers.GetAssemblyName(Project prj) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.CreateDebuggerStartInfo(VSBuildServerClient server, MonoTouchDevice device, MonoTouchFlavoredProject project, IVsDebugger2 debugger, Int32 debugPort, Int32 consolePort) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.GetDebugSession(VSBuildServerClient server, MonoTouchFlavoredProject project, MonoTouchDevice device, String outputDirectory, IVsDebugger2 debugger, IVsOutputWindowPane output, Int32& appConsolePort) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.DebugApplication(VSBuildServerClient server, MonoTouchDevice device, IVsOutputWindowPane output, MonoTouchProgressNotifier notifier, LogReader consoleLogReader) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.<>cDisplayClassa.b6(VSBuildServerClient server) at Xamarin.VisualStudio.IOS.Utilities.BuildServer.<>cDisplayClass881.<RunOnlyIfConnected>b__86() at System.Threading.Tasks.Task1.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at System.Threading.Tasks.Task1.getResult() at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.DebugLaunchHack(VSDBGLAUNCHFLAGS grfLaunch) ---> (Inner Exception #0) System.Runtime.InteropServices.COMException (0x80004005): Solution unavailable. at EnvDTE.Project.getUniqueName() at Xamarin.VisualStudio.ProjectInterfaceConverters.ToHierarchy(Project project) at Xamarin.VisualStudio.IOS.Utilities.Helpers.GetAssemblyName(Project prj) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.CreateDebuggerStartInfo(VSBuildServerClient server, MonoTouchDevice device, MonoTouchFlavoredProject project, IVsDebugger2 debugger, Int32 debugPort, Int32 consolePort) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.GetDebugSession(VSBuildServerClient server, MonoTouchFlavoredProject project, MonoTouchDevice device, String outputDirectory, IVsDebugger2 debugger, IVsOutputWindowPane output, Int32& appConsolePort) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.DebugApplication(VSBuildServerClient server, MonoTouchDevice device, IVsOutputWindowPane output, MonoTouchProgressNotifier notifier, LogReader consoleLogReader) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.<>cDisplayClassa.b6(VSBuildServerClient server) at Xamarin.VisualStudio.IOS.Utilities.BuildServer.<>c_DisplayClass881.<RunOnlyIfConnected>b__86() at System.Threading.Tasks.Task1.InnerInvoke() at System.Threading.Tasks.Task.Execute()<--- 0 0

    Wednesday, January 14, 2015 1:11 AM
  • User76375 posted

    Our development team is experiencing the same issue. Please let us know as soon as there is a fix. Thank You.

    Wednesday, January 14, 2015 2:06 AM
  • User13824 posted

    Thanks for the reports all. Just as a first quick update, if anyone is seeing this when deploying to physical iOS devices, there is one known issue that will cause a hang if the currently selected provisioning profile is invalid.

    You can check if you might be hitting that issue by looking in the most recent *.log file under %LOCALAPPDATA%\Xamarin\Log. The tell-tale symptom for that provisioning profile problem is a message similar to the following:

    error MT1006: Could not install the application '/Users/macuser/Library/Caches/Xamarin/mtbs/builds/iOSApp1/68d4897c38888c8e17a75c9de79105de/bin/iPhone/Debug/iOSApp1.app' on the device iPhone: Your application failed code-signing checks. Check your certificates, provisioning profiles, and bundle ids. Probably your device is not part of the selected provisioning profile

    Wednesday, January 14, 2015 4:22 AM
  • User75198 posted

    @BrendanZagaeski? Thanks for support. I quick checked my most recent devenv, iOSDesigner and SDKUpdate logs under %LOCALAPPDATA%\Xamarin\Log and there's no sign of error MT1006. I can also confirm I'm using a valid iOS provisioning profile. I'm able to build my Xamarin.iOS app in VS and deploy it to device via Xcode but would prefer to deploy and be able to debug through VS.

    Wednesday, January 14, 2015 5:15 AM
  • User75977 posted

    same problem, deploying by VS 2013 and VS Hangs.

    this is urgent, all team stopped working.

    are you working on a solution???

    Wednesday, January 14, 2015 8:36 AM
  • User98220 posted

    Hello,

    I'm having the same problem, debugging a previously working iOS app from VS2013 Update 4, with Xamarin 3.9.236. It hangs for a while and then I get the same stack trace in the Output window as Son Nguyen.

    Under %LOCALAPPDATA%\Xamarin\Log\12.0, the most recent log says the following:

    Xamarin.VisualStudio.Utilities Warning: 0 : [2015-01-14 09:51:12.3] WaitInUIThread Window threw an Exception. System.ComponentModel.Win32Exception (0x80004005): Not enough quota is available to process this command at MS.Win32.UnsafeNativeMethods.PostMessage(HandleRef hwnd, WindowMessage msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet) at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam) at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

    This exception is repeated many times per debug attempt.

    I've tried deleting the app from the phone, and doing a clean build, restarting phone, PC and Mac build host. Progress on this project is being blocked due to this.

    Wednesday, January 14, 2015 10:22 AM
  • User99375 posted

    I can confirm this issue. Deploying to device results in a locked up Visual Studio instance. New Xamarin releases seem to break way too often. :(

    Wednesday, January 14, 2015 10:42 AM
  • User17232 posted

    Also seeing this issue.

    Sorry can't find anything more to add to help diagnose.

    Nothing interesting in the logs at %LOCALAPPDATA%\Xamarin\Log\12.0

    Wednesday, January 14, 2015 12:33 PM
  • User727 posted

    @KymPhillpotts

    I'm in this exact same situation. Same issue, and logs aren't saying anything useful.

    Edit: Actually not entirely true. I should probably mention that I am using Xamarin Forms, so I'd guess the problem lies in either the Visual Studio tool, or the builder.

    Wednesday, January 14, 2015 2:09 PM
  • User58568 posted

    Also seeing this issue.

    Visual Studio hangs just after launching application to iOS device as well as iOS Simulator. ‘Visual Studio is busy’ bubble pops up. Visual Studio and app become unresponsive.

    We are using Xamarin Forms as well.

    No error MT1006 in our log files.

    Please advise!

    Wednesday, January 14, 2015 2:43 PM
  • User85265 posted

    My coworker and I are both experiencing the same thing. I was going to install VS update 4, but it seems people with update 4 are dealing with the same issue. This started for both of us when we installed the latest xamarin update with unified support (iOS 8.6.0.0).

    Mac side is Yosemite with all most recent xamarin/xcode updates.

    FWIW, Visual Studio help dialog version info:

    Microsoft Visual Studio Professional 2013 Version 12.0.30723.00 Update 3 Microsoft .NET Framework Version 4.5.51641

    Installed Version: Professional

    LightSwitch for Visual Studio 2013 06177-004-0446016-02824 Microsoft LightSwitch for Visual Studio 2013

    Team Explorer for Visual Studio 2013 06177-004-0446016-02824 Microsoft Team Explorer for Visual Studio 2013

    Visual Basic 2013 06177-004-0446016-02824 Microsoft Visual Basic 2013

    Visual C# 2013 06177-004-0446016-02824 Microsoft Visual C# 2013

    Visual Studio 2013 Code Analysis Spell Checker 06177-004-0446016-02824 Microsoft® Visual Studio® 2013 Code Analysis Spell Checker

    Portions of International CorrectSpell™ spelling correction system © 1993 by Lernout & Hauspie Speech Products N.V. All rights reserved.

    The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved.

    Windows Phone SDK 8.0 - ENU 06177-004-0446016-02824 Windows Phone SDK 8.0 - ENU

    AnkhSVN - Subversion Support for Visual Studio 2.5.12266.473 AnkhSVN - Subversion Support for Visual Studio 2.5.12266.473 * Ankh.Package 2.5.12266.473 * Subversion 1.8.4 via SharpSvn 1.8004.2605.15365

    SharpSvn is linked to: Apr 1.4.8, Apr-util 1.5.2, Cyrus Sasl 2.1.23, OpenSSL 1.0.1e 11 Feb 2013, serf 1.3.2, SQLite 3.7.17, Subversion 1.8.4-SharpSvn-1.8.4, ZLib 1.2.8 SharpSvn is optionally linked to: Berkeley DB 4.4.20, SharpPlink 1.8004.2605.15365

    Application Insights Tools for Visual Studio Package 1.0 Application Insights Tools for Visual Studio

    ASP.NET and Web Tools 12.3.50717.0 Microsoft Web Developer Tools contains the following components: Support for creating and opening ASP.NET web projects Browser Link: A communication channel between Visual Studio and browsers Editor extensions for HTML, CSS, and JavaScript Page Inspector: Inspection tool for ASP.NET web projects Scaffolding: A framework for building and running code generators Server Explorer extensions for Microsoft Azure Websites Web publishing: Extensions for publishing ASP.NET web projects to hosting providers, on-premises servers, or Microsoft Azure

    ASP.NET Web Frameworks and Tools 2012.2 4.1.21001.0 For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563

    ASP.NET Web Frameworks and Tools 2013 5.2.20703.0 For additional information, visit http://www.asp.net/

    Common Azure Tools 1.2 Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

    Microsoft Advertising SDK for Windows Phone
    Microsoft Advertising SDK for Windows Phone Build

    Microsoft Azure Mobile Services Tools 1.2 Microsoft Azure Mobile Services Tools

    NuGet Package Manager 2.8.50313.46 NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

    Office Developer Tools for Visual Studio 2013 ENU 12.0.30626 Microsoft Office Developer Tools for Visual Studio 2013 ENU

    PowerShell Tools 1.2 Provides file classification services using PowerShell

    PreEmptive Analytics Visualizer 1.2 Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

    SQL Server Data Tools 12.0.30919.1 Microsoft SQL Server Data Tools

    tangible T4 Editor 2.2.0 tangible engineering GmbH

    Windows Phone 8.1 SDK Integration 1.0 This package integrates the tools for the Windows Phone 8.1 SDK into the menus and controls of Visual Studio.

    Workflow Manager Tools 1.0 1.0 This package contains the necessary Visual Studio integration components for Workflow Manager.

    Xamarin 3.9.236.0 (d6a2cae) Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

    Xamarin.Android 4.20.0.34 (49a04b966feb40dfdba49d57ba16249b66d606a6) Visual Studio plugin to enable development for Xamarin.Android.

    Xamarin.iOS 8.6.0.0 (eb24bdcf5cba2c12b673a07e0a8cce368b9563b3) Visual Studio extension to enable development for Xamarin.iOS.

    Xamarin.iOS Unified Migration 1.0 Automated migration for Xamarin iOS Classic projects to Unified

    Wednesday, January 14, 2015 3:48 PM
  • User76375 posted

    @BrendanZagaeski? Thank you for the response but this is not the issue we are experiencing. The provisioning profile is valid, in fact it worked fine yesterday prior to the update. As others have mentioned, we can't move forward on development until there is a fix.

    Wednesday, January 14, 2015 4:09 PM
  • User13824 posted

    The issue is indeed under investigation by the Xamarin for Visual Studio developer and QA teams. Just to add one more possible cause, if you're using Xamarin Insights in your app, the Insights.Initialize() method has been reported to cause similar symptoms. Removing that method call might help with the problem in some cases.

    To be thorough, I'll also post a quick link to an article about downgrading in case that might be the fastest workaround for any users who are hitting the problem: http://kb.xamarin.com/customer/portal/articles/1699777-downgrading (This link should open an article titled "Downgrading". Due to some of the login code on xamarin.com, you might have to navigate to the link twice to get the correct article to appear.)

    For trial users (who won't see old versions on their store.xamarin.com account page), here are the download links for the previous stable versions:

    Wednesday, January 14, 2015 4:26 PM
  • User40541 posted

    @BrendanZagaeski? I was experiencing the Visual Studio 2013 hang when launching my app. I reverted to the previous version of Xamarin for Visual Studio and Xamarin.iOS. I didn't follow the downgrading article you mentioned. I only followed the Uninstall Xamarin Studio part of: http://developer.xamarin.com/guides/cross-platform/gettingstarted/installation/uninstallingxamarin/#UninstallXamarinStudio

    I did not do the Uninstall Mono SDK (MDK) part.

    At this point I threw the following exception when launching my app:

    Unhandled managed exception: Corrupted data ReadInternal (System.IO.IOException) at System.IO.Compression.DeflateStreamNative.CheckResult (Int32 result, System.String where) [0x000a5] in /Developer/MonoTouch/Source/monotouch/build//Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/System/System.IO.Compression/DeflateStream.cs:477 at System.IO.Compression.DeflateStreamNative.ReadZStream (IntPtr buffer, Int32 length) [0x0000e] in /Developer/MonoTouch/Source/monotouch/build//Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/System/System.IO.Compression/DeflateStream.cs:375 at System.IO.Compression.DeflateStream.ReadInternal (System.Byte[] array, Int32 offset, Int32 count) [0x0002f] in /Developer/MonoTouch/Source/monotouch/build//Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/System/System.IO.Compression/DeflateStream.cs:125 at System.IO.Compression.DeflateStream.Read (System.By te[] dest, Int32 destoffset, Int32 count) [0x00086] in /Developer/MonoTouch/Source/monotouch/build//Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/System/System.IO.Compression/DeflateStream.cs:145 at System.IO.Compression.GZipStream.Read (System.Byte[] dest, Int32 destoffset, Int32 count) [0x0001c] in /Developer/MonoTouch/Source/monotouch/build//Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/mcs/class/System/System.IO.Compression/GZipStream.cs:80 at Xamarin.InsightsCore.IOWriter.ReadDiskImage (System.String fileName) [0x00000] in :0 at Xamarin.InsightsCore.CachedString..ctor (System.String id, Boolean doNotHash) [0x00000] in :0 at Xamarin.InsightsCore.Core..ctor () [0x00000] in :0 at Xamarin.InsightsCore.Device.getCore () [0x00000] in :0 at Xamarin.Insights.Initialize (System.String apiKey) [0x00000] in :0

    I suspect that there may be a problem with the latest MDK which causes this exception.

    I removed all Insights code from my project. Everything worked, the application launched and debugged in Visual Studio 2013. I re-updated to the latest versions of Xamarin for Visual Studio and Xamarin.iOS. Everything still works! Other than Insights, that is.

    I suspect that there may also be a problem with the way the latest Xamarin for Visual Studio works with the debugger and the Corrupted data ReadInternal exception, compared to previous versions.

    Thursday, January 15, 2015 1:28 AM
  • User17232 posted

    FWIW, I downgraded my VS client and mac build host and am now able to debug onto Simulator and Device. Thanks for the workaround @BrendanZagaeski?

    Looking forward to that patch though ;-)

    Thursday, January 15, 2015 4:42 AM
  • User75977 posted

    for me it's a very bad solution to downgrade

    i have already upgraded all my project's to be unified, and now rollback is not an option.

    Thursday, January 15, 2015 10:05 AM
  • User76375 posted

    The downgrade option also does not work for us as we have migrated our code to unified. It does not allow us to deploy to device for debugging. I believe the old version contains only a preview of the unified framework which throws an error when compiling for devices. I also tried the workaround provided by @BrendanZagaeski? but this did not work. Can you please update us on the progress of this issue? It is becoming a real impediment for our development team.

    Thursday, January 15, 2015 4:05 PM
  • User13824 posted

    We have an experimental preview build available that might help for some cases where Visual Studio is hanging. It primarily targets a problem where Visual Studio will hang if it is unable to connect to and start debugging an iOS app.

    Just to reiterate, this build includes new untested changes, so even if it helps with the hanging problem it's possible it might introduce some other issues.

    Those cautions out of the way, here's the build for anyone who might like to try it:
    http://xvs.xamarin.com/Xamarin.VisualStudio_3.9.246.msi

    Thursday, January 15, 2015 8:39 PM
  • User76375 posted

    Thank you for the update. I installed it and, unfortunately, ran into the same issue.

    Thursday, January 15, 2015 9:55 PM
  • User62771 posted

    For reference, after waiting 30 or so mins, this was the error thay usualy hangs or pops up an alert that VS2013 is busy

    Error   1   There was an unhandled exception trying to deploy and run your application.
    System.AggregateException: One or more errors occurred. ---> System.ArgumentException: Debug port cannot be zero when connecting
    Parameter name: debugPort
       at Mono.Debugging.Soft.SoftDebuggerConnectArgs..ctor(String appName, IPAddress address, Int32 debugPort, Int32 outputPort)
       at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.CreateDebuggerStartInfo(VSBuildServerClient server, MonoTouchDevice device, MonoTouchFlavoredProject project, IVsDebugger2 debugger, Int32 debugPort, Int32 consolePort)
       at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.GetDebugSession(VSBuildServerClient server, MonoTouchFlavoredProject project, MonoTouchDevice device, String outputDirectory, IVsDebugger2 debugger, IVsOutputWindowPane output, Int32& appConsolePort)
       at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.DebugApplication(VSBuildServerClient server, MonoTouchDevice device, IVsOutputWindowPane output, MonoTouchProgressNotifier notifier, LogReader consoleLogReader)
       at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.<>c__DisplayClassa.b__6(VSBuildServerClient server)
       at Xamarin.VisualStudio.IOS.Utilities.BuildServer.<>c__DisplayClass88`1.b__86()
       at System.Threading.Tasks.Task`1.InnerInvoke()
       at System.Threading.Tasks.Task.Execute()
       --- End of inner exception stack trace ---
       at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
       at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
       at System.Threading.Tasks.Task`1.get_Result()
       at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.DebugLaunchHack(__VSDBGLAUNCHFLAGS grfLaunch)
    ---> (Inner Exception #0) System.ArgumentException: Debug port cannot be zero when connecting
    Parameter name: debugPort
       at Mono.Debugging.Soft.SoftDebuggerConnectArgs..ctor(String appName, IPAddress address, Int32 debugPort, Int32 outputPort)
       at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.CreateDebuggerStartInfo(VSBuildServerClient server, MonoTouchDevice device, MonoTouchFlavoredProject project, IVsDebugger2 debugger, Int32 debugPort, Int32 consolePort)
       at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.GetDebugSession(VSBuildServerClient server, MonoTouchFlavoredProject project, MonoTouchDevice device, String outputDirectory, IVsDebugger2 debugger, IVsOutputWindowPane output, Int32& appConsolePort)
       at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.DebugApplication(VSBuildServerClient server, MonoTouchDevice device, IVsOutputWindowPane output, MonoTouchProgressNotifier notifier, LogReader consoleLogReader)
       at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.<>c__DisplayClassa.b__6(VSBuildServerClient server)
       at Xamarin.VisualStudio.IOS.Utilities.BuildServer.<>c__DisplayClass88`1.b__86()
       at System.Threading.Tasks.Task`1.InnerInvoke()
       at System.Threading.Tasks.Task.Execute()<---
            0   0   
    
    
    Friday, January 16, 2015 3:05 PM
  • User13824 posted

    For anyone who has tried the experimental 3.9.246 build but is still seeing a problem, there is one more experiment you can try based on some in-progress investigation by the XamarinVS team:

    Check if disabling the ReSharper extension helps.

    Friday, January 16, 2015 8:29 PM
  • User76375 posted

    Thank you Brendan. We do not have ReSharper installed, so this isn't the issue for us. Just letting you know so you can pass that information along if need be.

    Friday, January 16, 2015 9:57 PM
  • User83725 posted

    Brendan, do you have any info about the bug? has it been identified? When can we expect to get a fix? Same here as others, all developments stopped!

    Saturday, January 17, 2015 10:21 AM
  • User865 posted

    I'm soooo tired of Xamarin Updates :-( Every time I'm installing a new update, I always is expiring problems. After the new price model has been implemented and the company has grown into a big company. I would like to have a more stabel version of every single update. There are real companyes, building real apps for real consumers, that relys on your product. It is not good that we are expiring setbacks every single time you guys publish a new update!

    Sunday, January 18, 2015 10:34 AM
  • User53165 posted

    +1 Our dev team is seeing this issue. Our development has effectively stopped too (well, let's just say our devs are now rolling around the office on their chairs having sword fights, which according to them is actually an accepted part of software development - not sure I agree).

    Monday, January 19, 2015 3:55 AM
  • User73524 posted

    Same problem. Works ok deploying to iOS emulator and Android emulator as well as a physical Android device -- but hangs Visual Studio when deploying to a physical iOS device. I'll just work on stuff that I can with the emulators. Hope to see this fixed soon!

    BTW, thanks ya'll for the forward momentum -- some of the problems that I was having with Forms.Maps are fixed so I'm sure this is just a two steps forward, one step back situation.

    Monday, January 19, 2015 6:17 AM
  • User98220 posted

    I've tried version 3.9.246, and the problem still occurs. I then tried disabling ReSharper. This didn't help either.

    The same error occured in the Xamarin log:


    Xamarin.VisualStudio.Utilities Warning: 0 : [2015-01-19 11:33:55.1] WaitInUIThread Window threw an Exception. System.ComponentModel.Win32Exception (0x80004005): Not enough quota is available to process this command at MS.Win32.UnsafeNativeMethods.PostMessage(HandleRef hwnd, WindowMessage msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet) at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam) at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) Xamarin.VisualStudio.IOS.XamarinIOSPackage Information: 0 : [2015-01-19 11:33:55.1] [19-Jan-2015 11:33:46] Warning: Device selection wait timed out (waited 00:05:00) Xamarin.VisualStudio.IOS.XamarinIOSPackage Information: 0 : [2015-01-19 11:33:55.1] [19-Jan-2015 11:33:46] Command [StartDebugProxy: CommmandUrl=StartDebugProxy] finished (11)

    Xamarin.VisualStudio.IOS.XamarinIOSPackage Information: 0 : [2015-01-19 11:33:55.1] [19-Jan-2015 11:33:46] Request handled in 300050.786ms

    Is there any more info I can supply that might help?

    Monday, January 19, 2015 11:36 AM
  • User63744 posted

    +1

    My team upgraded to the latest version so we can migrate to unified and now this happens. Can't do anything on a real device for days now. This is a huge disappointment really. Every now and then my projects grind to a halt because of a bad Xamarin update. As someone mentioned previously rolling back is not an option because of the unified support.

    Monday, January 19, 2015 1:48 PM
  • User22737 posted

    Same issue here. Debugging on the iOS simulator is not possible! Is there any new information ... or at least hope ?

    Monday, January 19, 2015 2:12 PM
  • User40444 posted

    Same issue here. Any ETA available ?

    Monday, January 19, 2015 3:12 PM
  • User3412 posted

    same here... waiting for a fix - asap!

    Monday, January 19, 2015 4:34 PM
  • User13824 posted

    One more little update to confirm that the team has been working steadily on the problem: there is another build underway right now. I'll update the thread once that build has completed and once the QA team has quickly verified that it improves the behavior. (See also the most recent update on the corresponding thread for hanging on Android apps: https://forums.xamarin.com/discussion/comment/98023/#Comment_98023.)

    Monday, January 19, 2015 5:17 PM
  • User13824 posted

    Here's another experimental preview build that might help for at least some users. To repeat the warnings from before, this build includes new untested changes, so even if it helps with the hanging problem it's possible it might introduce some other issues.

    Those cautions out of the way, here's the build for anyone who might like to try it:
    http://xvs.xamarin.com/Xamarin.VisualStudio_3.9.274.msi

    Tuesday, January 20, 2015 4:44 AM
  • User40444 posted

    Thank you for the update. Looking forward to see those fixes.

    Tuesday, January 20, 2015 8:10 AM
  • User40444 posted

    i found some workaround for this issue. When i build and deploy the iOS app to the simulator and stop it after it started successfully, i am able to choose my ios provisioning profile and build and deploy on the device (and this is working most of the time).

    Hope this might help somebody.

    Tuesday, January 20, 2015 9:21 AM
  • User15281 posted

    Wow, 3.9.274 works great for me! VS no longer hangs up after launching failure.

    Tuesday, January 20, 2015 1:14 PM
  • User22737 posted

    Same here. 3.9.274 works also for me!

    Tuesday, January 20, 2015 2:49 PM
  • User97920 posted

    Hoping to solve the problems, I installed this file http://xvs.xamarin.com/Xamarin.VisualStudio_3.9.274.msi but now I can't connect to the mac anymore. My current versions are:

    Xamarin 3.9.274 Xamarin.Android 4.20.0.34 Xamarin.iOS 8.6.1.0

    and Xamarin says me that there is a new update available : 3.9.236

    What can I do to solve the problem?

    EDIT: I solve my problem using the manual configuration. Sorry...

    I'm testing this version and I will tell you I the problems are solved!

    Tuesday, January 20, 2015 3:25 PM
  • User67851 posted

    Finally - 3.9.274 definitely works! You can download it from this link: http://xvs.xamarin.com/Xamarin.VisualStudio_3.9.274.msi

    Tuesday, January 20, 2015 3:26 PM
  • User65389 posted

    3.9.274 don't work for me (same or worse behavior as before).

    Tuesday, January 20, 2015 4:18 PM
  • User85265 posted

    3.9.274 is working for me. Thanks for the update!

    For anyone else interested, the steps I took were:

    • Upgrade Mac version to latest from the stable channel (I had downgraded previously). Build host is at Xamarin.iOS 8.6.0.51.
    • Install Windows 3.9.274 version

    At this point I launched VS and then the app. It worked, but I got a weird debugger error (attached) and I had to end the VS task. So:

    • I rebooted both the Mac and PC
    • Then launched VS and the app again.

    So far so good, everything seems to be working.

    Tuesday, January 20, 2015 5:29 PM
  • User76375 posted

    This seems to be working for us too. Thank you!

    Tuesday, January 20, 2015 7:10 PM
  • User75198 posted

    Xamarin Visual Studio build 3.9.274.0 does not work for me.

    It has changed the issue though. Now VS doesn't freeze when attempting on device debugging. Instead nothing happens when clicking "Start Debugging" and the Debug Output window never prints anything after "Launching Application for debugging...". I should add that clicking "Start Without Debugging" does deploy and launch that app as intended.

    Here's my Xamarin environment:

    PC:

    VS2013 Update 4, ReSharper 8.2, Xamarin 3.9.274.0, Xamarin.Android 4.20.0.34, Xamarin.iOS 8.6.1.0, Xamarin.iOS Unified Migration 1.0,

    Mac build host:

    Xcode 6.1.1, Xamarin Build Host 3.9.0.234, Xamarin.iOS 8.6.0.51, Xamarin.Android 4.20.028,

    * UPDATE *

    I had also tried restarting my Mac, PC and iPhone without success, but after manually launching Xcode on the Mac build host and trying again then Visual Studio Debugging worked! I have now closed Xcode on the Mac build host and on device debugging continues to work via Visual Studio.

    Tuesday, January 20, 2015 7:55 PM
  • User75831 posted

    Mine is not working with the new build either :(. The application still runs, but the debugger does not attach. In my instance - the debug output window will load all the assemblies: "Loaded assembly: /Users/name/Library/Developer/CoreSimulator/Devices/---/data/Containers/Bundle/Application/---.dll" etc and the status will be stuck on "Launching Application for Debugging".

    EDIT -- Tried the solutions above and below which give me the same results. Gahhhh, how frustrating...

    Tuesday, January 20, 2015 8:14 PM
  • User76375 posted

    @SonNguyen.3151 I had that issue too. This is what I did to get it to work correctly:

    1. After the install rebooted both machines
    2. In Simulator went to iOS Simulator > Reset Content and Settings.
    3. Clean build in Visual Studio on project
    4. Pair the two
    5. Debug works as expected
    Tuesday, January 20, 2015 8:14 PM
  • User77428 posted

    Hi Folks, we are continuing to investigate reports of hangs on iOS devices and we believe that Xamarin.VisualStudio_3.9.274 contains the necessary fixes for the iOS hangs and that the debugger successfully attaches.

    We have seen several customers with incorrect iOS Bundle signing and Provisioning profile settings that have been resolved by going into Xcode-->Preferences-->AppleIds-->ViewDetials and ensuring the Signing Identities are present, in addition going to Xcode, creating a new project, opening the project details, clicking Team and ensuring that the provisioning profile is successfully registered in Xcode.

    Additionally, attempting to the debug the application in VS a second time does resolve any cached/stale results.

    We have have several customers successfully install this hotfix and have seen the hang issues be resolved for iOS.

    After installing this hotfix build i'd like to ask you to send everyone to please send me a quick mail indicating if you've seen the hang issue being resolved or if it is in fact not resolved. any additional feedback/issues you are seeing so I can make additional improvements.

    Ian Ceicys :: Visual Studio QA Software Engineer @ Xamarin - title :: Ian.Ceicys@Xamarin.com - email :: (440)724-6721 - phone.mobile

    Tuesday, January 20, 2015 11:36 PM
  • User865 posted

    The update 3.9.274 worked also for me :-)

    Wednesday, January 21, 2015 12:48 PM
  • User41265 posted

    I cannot debug app in ios device (iPhone), but in ios simulator everything works fine. Error 22 error MT1007: Failed to launch the application '' on the device 'iPhone dev': Look for earlier warnings returned: 0x454. You can still launch the application manually by tapping on it. Xamarin.iOS Extension 0 0

    Thursday, January 22, 2015 9:40 AM
  • User53165 posted

    @RADev? I had a similar issue. It would build fine, but then would just do nothing at the Launching Application stage. I had to reselect my iPhone from the drop down in VS - no need to select anything else, just press the little drop down and select it again...

    Hope my little over simple answer helps :)

    JK

    Thursday, January 22, 2015 10:32 PM
  • User53165 posted

    3.9.274 has worked for me too. We had a full day with no hangs.

    Thursday, January 22, 2015 10:33 PM
  • User11280 posted

    Hi guys, 3.9.274 works for me!

    Friday, January 23, 2015 9:41 PM
  • User65389 posted

    @Xamarin-Ian?:

    Any news on this?

    As you know, there are various developers, where the update don't work (like me) and this is a blocker for the daily work.

    See also: forums.xamarin.com/discussion/27775/visual-studio-hangs-while-debugging-in-ios#latest

    and
    forums.xamarin.com/discussion/12048/droid-debugging-visual-studio-is-busy#latest

    Monday, January 26, 2015 12:49 PM
  • User65389 posted

    Updatet to XF 1.3.2-Pre-1:
    Same behavior:

    Debug to Android:
    - Breakpoint is showed in VS
    - "Spinning wheel" is showed
    - VS is frozen and has to be canceled in TaskManager
    Debug to iOS:
    - Breakpoint is reached and showed in VS
    - Then - after a few seconds - the Connection to the MAC is lost

    So.. only platform now, that works for me, is WP.

    Monday, January 26, 2015 2:58 PM
  • User27993 posted

    3.9.274 has solved the issue for me; I would feel a whole lot better knowing the cause has been identified and that it's fixes for everything though, until then I'm keeping my finger well away from the Update button. Cheers for being proactive about solving this however, and good luck for the remaining problems.

    Monday, January 26, 2015 9:57 PM
  • User97920 posted

    With the new version (3.9.274) the problem seems solved, but there are also several other related problems. When a breakpoint is reached during ios debugging, after few seconds, the application terminates. But the worst problem is with the ios designer, every few minutes it crashes. I reported the problem on the bug tracking system. I hope it will be solved very soon.

    Tuesday, January 27, 2015 8:42 AM
  • User13824 posted

    A small update: the XamarinVS version that was published to the Alpha updater channel today (3.9.289) includes the fixes that were in 3.9.274 plus just a few other changes. So anyone who is hitting debugger hangs with 3.9.236 can feel free to update directly to 3.9.289 via the updater. Two key issues that were fixed for 3.9.274 (and are included in 3.9.289) were: (1) a problem that could cause the soft debugger to deadlock when polling the threads of the running app, and (2) a few scenarios that could cause Visual Studio to hang when the VS debugger had trouble connecting with the soft debugger agent in the app.

    There is still at least one known, precisely defined scenario that will cause VS to get stuck in a busy state for about 2 minutes in 3.9.289. This can happen if an iOS app launches successfully but then crashes before the Main() method runs. At present the only reported cause of this kind of crash is if the "iOS Build -> Enable incremental build" is enabled. Investigation of this issue and further stress testing of 3.9.289 will be performed in preparation for a follow-up alpha release (after the 3.9.289 branch has moved to stable).

    Thursday, January 29, 2015 6:24 AM
  • User65389 posted

    @BrendanZagaeski:
    I see error-messages in Fiddler about every second after I have started VS2013 (to /ListDevices?ShowDeviceVersion=True).
    I have submitted this three times now to Xamarin and never have received any feedback. In the attached .pdf you can see some screenshots.
    May I have an answer to that problem please!

    Maybe this problem is only related to my installation, maybe it is a general problem...?
    But I simply want a feedback to...
    Thanks

    Thursday, January 29, 2015 9:27 AM
  • User13824 posted

    @FredyWenger, from a quick glance through old reports of "400 Bad Request" server errors, it sounds like Fiddler itself might be causing that particular problem. It seems that Fiddler turns on the Windows network proxy and that causes the problem. I believe http://forums.xamarin.com/discussion/25470/false-communication-with-mac was one of your previous reports about the problem? Since that issue seems to be an on-going problem that also existed in XamarinVS 3.8 (and probably earlier), the best way to proceed with that particular problem would be to file a bug report on http://bugzilla.xamarin.com, being sure to include as many of the details mentioned on https://bugzilla.xamarin.com/page.cgi?id=bug-writing.html as possible. If you like, you can instead send your draft bug report to one of the support email addresses listed on http://store.xamarin.com/account/ and mention my name in the email. I'll then pick up on the email thread to make sure the Xamarin developers will have a complete set of steps to reproduce plus precise descriptions of the observed and expected results, and I'll file a bug report.

    I did a few quick searches of Bugzilla to see if there might have already been a report for the "400 Bad Request" issue, but I didn't find anything matching. I might have missed it. If you have already filed a bug for that issue, feel free to include the bug number in your email (to one of the support addresses on http://store.xamarin.com/account/), and I'll review it.

    We can take a similar approach for the other issues you reported earlier in the thread if you're still seeing them. Thanks in advance!

    Thursday, January 29, 2015 7:31 PM
  • User65389 posted

    @BrendanZagaeski: Thanks for your feedback. Yes, the false communication was the same theme. As I wrote here in the thread's I am not able to debug iOS and Android (only working Platform is WP). This since about a week now!
    I already have sent my whole project and various details to the problems to Ian.
    To Fiddler, I try to find-out, if fiddler himself can cause the problem.

    Thursday, January 29, 2015 8:17 PM
  • User15652 posted

    The new version (3.9.236.0) has actually created this problem for me. I did not have this problem with last version, and now that I have updated yesterday - it has been an absolute nightmare as I am only able to get my solution to compile in Xamarin Studio on the MacBook and not from Visual Studio with iOS Build Host. I continually receive this error over and over and over...

    Error 2 There was an unhandled exception trying to deploy and run your application. System.AggregateException: One or more errors occurred. ---> System.Runtime.InteropServices.COMException: Solution unavailable. at EnvDTE.Project.get_UniqueName() at Xamarin.VisualStudio.ProjectInterfaceConverters.ToHierarchy(Project project) at Xamarin.VisualStudio.IOS.Utilities.Helpers.GetAssemblyName(Project prj) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.CreateDebuggerStartInfo(VSBuildServerClient server, MonoTouchDevice device, MonoTouchFlavoredProject project, IVsDebugger2 debugger, Int32 debugPort, Int32 consolePort) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.GetDebugSession(VSBuildServerClient server, MonoTouchFlavoredProject project, MonoTouchDevice device, String outputDirectory, IVsDebugger2 debugger, IVsOutputWindowPane output, Int32& appConsolePort) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.DebugApplication(VSBuildServerClient server, MonoTouchDevice device, IVsOutputWindowPane output, MonoTouchProgressNotifier notifier, LogReader consoleLogReader) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.<>c__DisplayClassa.<DebugLaunchHack>b__6(VSBuildServerClient server) at Xamarin.VisualStudio.IOS.Utilities.BuildServer.<>c__DisplayClass881.b86() at System.Threading.Tasks.Task1.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification) at System.Threading.Tasks.Task1.get_Result() at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.DebugLaunchHack(__VSDBGLAUNCHFLAGS grfLaunch) ---> (Inner Exception #0) System.Runtime.InteropServices.COMException (0x80004005): Solution unavailable. at EnvDTE.Project.get_UniqueName() at Xamarin.VisualStudio.ProjectInterfaceConverters.ToHierarchy(Project project) at Xamarin.VisualStudio.IOS.Utilities.Helpers.GetAssemblyName(Project prj) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.CreateDebuggerStartInfo(VSBuildServerClient server, MonoTouchDevice device, MonoTouchFlavoredProject project, IVsDebugger2 debugger, Int32 debugPort, Int32 consolePort) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.GetDebugSession(VSBuildServerClient server, MonoTouchFlavoredProject project, MonoTouchDevice device, String outputDirectory, IVsDebugger2 debugger, IVsOutputWindowPane output, Int32& appConsolePort) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.DebugApplication(VSBuildServerClient server, MonoTouchDevice device, IVsOutputWindowPane output, MonoTouchProgressNotifier notifier, LogReader consoleLogReader) at Xamarin.VisualStudio.IOS.MonoTouchFlavoredProject.<>c__DisplayClassa.<DebugLaunchHack>b__6(VSBuildServerClient server) at Xamarin.VisualStudio.IOS.Utilities.BuildServer.<>c__DisplayClass881.b86() at System.Threading.Tasks.Task1.InnerInvoke() at System.Threading.Tasks.Task.Execute()<--- 0 0

    Microsoft Visual Studio Professional 2013 Version 12.0.31101.00 Update 4 Microsoft .NET Framework Version 4.5.51641

    Installed Version: Professional

    Team Explorer for Visual Studio 2013 06177-004-0446043-02577 Microsoft Team Explorer for Visual Studio 2013

    Visual Basic 2013 06177-004-0446043-02577 Microsoft Visual Basic 2013

    Visual C# 2013 06177-004-0446043-02577 Microsoft Visual C# 2013

    Visual C++ 2013 06177-004-0446043-02577 Microsoft Visual C++ 2013

    Visual F# 2013 06177-004-0446043-02577 Microsoft Visual F# 2013

    Visual Studio 2013 Code Analysis Spell Checker 06177-004-0446043-02577 Microsoft® Visual Studio® 2013 Code Analysis Spell Checker

    Portions of International CorrectSpell™ spelling correction system © 1993 by Lernout & Hauspie Speech Products N.V. All rights reserved.

    The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved.

    Windows Phone SDK 8.0 - ENU 06177-004-0446043-02577 Windows Phone SDK 8.0 - ENU

    Advanced Installer Extension 11.7.1 Advanced Installer Extension. For more information visit the Advanced Installer website at www.advancedinstaller.com. Copyright © Caphyon LTD. All rights reserved.

    Application Insights Tools for Visual Studio Package 1.0 Application Insights Tools for Visual Studio

    ASP.NET and Web Tools 12.4.51016.0 Microsoft Web Developer Tools contains the following components: Support for creating and opening ASP.NET web projects Browser Link: A communication channel between Visual Studio and browsers Editor extensions for HTML, CSS, and JavaScript Page Inspector: Inspection tool for ASP.NET web projects Scaffolding: A framework for building and running code generators Server Explorer extensions for Microsoft Azure Websites Web publishing: Extensions for publishing ASP.NET web projects to hosting providers, on-premises servers, or Microsoft Azure

    ASP.NET Web Frameworks and Tools 2012.2 4.1.21001.0 For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563

    ASP.NET Web Frameworks and Tools 2013 5.2.21010.0 For additional information, visit http://www.asp.net/

    Common Azure Tools 1.3 Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

    Microsoft Advertising SDK for Windows Phone
    Microsoft Advertising SDK for Windows Phone Build

    Microsoft Azure Mobile Services Tools 1.3 Microsoft Azure Mobile Services Tools

    NuGet Package Manager 2.8.50926.663 NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

    PowerShell Tools 1.3 Provides file classification services using PowerShell

    PreEmptive Analytics Visualizer 1.2 Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

    SQL Server Data Tools 12.0.41012.0 Microsoft SQL Server Data Tools

    VisualGDB 4.2 Allows developing and debugging Embedded, Linux, Android and other GCC/GDB-based applications with Visual Studio.

    Windows Phone 8.1 SDK Integration 1.0 This package integrates the tools for the Windows Phone 8.1 SDK into the menus and controls of Visual Studio.

    Xamarin 3.9.236.0 (d6a2cae) Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

    Xamarin.Android 4.20.0.34 (49a04b966feb40dfdba49d57ba16249b66d606a6) Visual Studio plugin to enable development for Xamarin.Android.

    Xamarin.iOS 8.6.0.0 (eb24bdcf5cba2c12b673a07e0a8cce368b9563b3) Visual Studio extension to enable development for Xamarin.iOS.

    Xamarin.iOS Unified Migration 1.0 Automated migration for Xamarin iOS Classic projects to Unified

    Saturday, January 31, 2015 12:53 AM
  • User23807 posted

    Another 14 days are gone and still no solution for this issue. Come on Xamarin, we are waiting for a fix.

    Sunday, February 1, 2015 5:54 PM
  • User13824 posted

    @MartinRothschink, the alpha version (3.9.289) currently available via the updater channels has resolved the issue for many users. The developer and QA teams are currently still investigating individual cases where this version has not been sufficient to resolve regressions between 3.8.150 and the 3.9 series. If you have a reproducible regression that's causing VS to hang when working with iOS projects in XamarinVS 3.9.289 but not in XamarinVS 3.8.150, please get in touch either via an email to the support team (using one of the email addresses listed on http://store.xamarin.com/account/) or directly to Ian (as discussed in his earlier post in this thread: http://forums.xamarin.com/discussion/comment/98386/#Comment_98386). If you write to the support team, feel free to mention my name in the email to make sure it gets prioritized properly. Thanks in advance!


    EDIT 4:51 PM: Reword reproducible regression sentence for accuracy. Add missing link to Ian's earlier post.

    Sunday, February 1, 2015 9:47 PM
  • User23053 posted

    I have updated to 3.9.289, and still no resolution for debugging from VS. Simple hangs at application launch. Works fine on Xam on the Mac.

    Tuesday, February 3, 2015 6:41 PM
  • User23807 posted

    Thanks, with the alpha version it looks a lot better now.

    Tuesday, February 3, 2015 8:51 PM
  • User97920 posted

    With the ios debugger, within 10 - 15 seconds, the debugger stops and the app quits. Pratically the debugger is useless.

    I love Xamarin but considering the price, these errors are inadmissible!

    Wednesday, February 4, 2015 9:35 AM
  • User79866 posted

    I am seeing the same lockup, I have tried killing XCode, Xamarin.IOS Build Host and the Simulator and nothing will stop hanging Visual Studio. I have to keep killing the process in Task Manager. I have also changed to the Alpha channel on both PC and Mac and still same results. Frustrating. This is why I purchased the Business license to use Visual Studio, but this is useless. Using Visual Studio 2013 with latest service pack.

    Wednesday, February 4, 2015 9:49 PM
  • User61537 posted

    OK - just adding my voice to the chorus now. This issue needs to be fixed please. I too am using VS2013 latest service pack (with resharper) Come on Xamarin - where is the patch love???

    Wednesday, February 4, 2015 10:24 PM
  • User83484 posted

    Updating to 3.9.289 also didn't help for me. If you need further information for debugging this issue just ask.

    Wednesday, February 4, 2015 10:58 PM
  • User79866 posted

    I submitted a support request to Xamarin and in their email reply it said to include the files from the "C:\Users[YOUR USER NAME[\AppData\Local\Xamarin\Log" directory on the PC. I looked in this directory and browsed the files and saw a bunch of errors about not being able to copy to this directory on my Mac: "/Users/[YOUR USER NAME]/Library/Caches/Xamarin/mtbs/builds/[YOUR APP NAME]"
    I ran "rmdir -r [YOUR APP NAME]" from the builds directory and now it works for now.

    Look in your most recent log file on your PC and see if any of you see this exception: UNHANDLED EXCEPTION: System.ArgumentOutOfRangeException: startIndex > this.length It was in my "C:\Users[YOUR USER NAME[\AppData\Local\Xamarin\Log\12.0" directory

    Thursday, February 5, 2015 5:04 AM
  • User20972 posted

    Updating to 3.9.289 also didn't help for me. If you need further information for debugging this issue just ask.

    We updated, booted/restarted/reset machines, ios simulator, etc... No change.

    App appears in ios simulator, launches, and then is unresponsive to input. VS2013 continues to display "Launching Application for debugging...". Nothing changed overnight.

    Friday, February 6, 2015 3:48 PM
  • User105983 posted

    Btw, disabling resharper worked for me without changing the build. Thanks for the suggestion!

    Friday, February 6, 2015 6:09 PM
  • User28977 posted

    Here's an interesting one from me:

    After not being able to start applications on iOS devices with or without debugging from VS for a couple of weeks now I upgraded to 3.9.289.0 (39a70ae) this morning, and SUDDENLY deploy to device started working. That was until I accidentally bumped the "Migrate to Xamarin.iOS Unified" button (side note: whoever placed it where the "Build" item of the project context menu usually is, gets no love from me). After carefully undoing the carnage brought about by the above, I am now unable to deploy to device again.

    Tuesday, February 10, 2015 6:34 AM
  • User65389 posted

    @all reader of this thread: There are various problems with the debugger (iOS and Android) right now (I'm not able to debug iOS and Android now for months). There also are various threads in the VS-Forum, very confusing and time-consuming. Therefore, I have opened a new thread (proposal to solve the problems on a new and professional way):

    forums.xamarin.com/discussion/33738/proposal-solving-of-the-debugger-problems-version-3-9-302#latest

    But... this seems to interest nobody (not Xamarin and also not the other pained users).
    So.. If you want to change something, read the thread and vote...!

    Thursday, February 26, 2015 1:59 PM
  • User38833 posted

    I just upgraded to the most stable releases yesterday and noticed today all my builds (if not most) get stuck on "Launching application for debugger"

    I don't want to go through the pains of downgrading. We should never have to downgrade, this is not where a stable release should result, ever.

    Tuesday, March 31, 2015 3:49 PM
  • User65389 posted

    Since today (after update to 1.4.1 (stable)) I additionally am not longer able to debug to my IPad-device: :angry:

    error MT1007: Failed to launch the application 'com.yourcompany.MatrixGuide' on the device 'iPad MATRIX Solutions AG': Look for earlier warnings returned: 0x454. You can still launch the application manually by tapping on it. Xamarin.iOS Extension 0

    This is new in my "collection" (the iPad was the "last standing" device, that has half worked for debugging).
    So... actually, I am not able to debug meaningful to iOS-Devices, iOS-Emulators and Android-devices.
    But hey.... who cares... Simply unbelievable!

    Tuesday, March 31, 2015 4:29 PM
  • User13824 posted

    Hi David and Fredy, that most recent issue (from today) sounds like it might be Bug 28027, mentioned on the XamarinVS 3.9.525 and XamarinVS 3.9.483 release threads.

    To further confirm if you're hitting that same bug (so that I can increase its priority), I'd be curious to know:

    • Does deploying to an iOS simulator succeed (at least most of the time)?

    • Does the problem happen every time you attempt to deploy to an iOS device, or does it occasionally succeed? (In my local tests for bug 28027, I saw successful launches on about 3/16 attempts.)

    • Does the app launch on the device but then the VS debugger never connects to the app? (In my tests, the app starts on the device, but VS never connects.)

    Thanks in advance.

    Tuesday, March 31, 2015 7:25 PM
  • User65389 posted

    @BrendanZagaeski:

    Does deploying to an iOS simulator succeed (at least most of the time)?

    After start of VS2013, it works one time
    Mostly the second time don’t work. Error Message “Failed to start application on the target simulator” I then have to restart VS to be able to start the debugging one more time

    Does the problem happen every time you attempt to deploy to an iOS device, or does it occasionally succeed? (In my local tests for bug 28027, I saw successful launches on about 3/16 attempts.)

    Yes, every time

    Does the app launch on the device but then the VS debugger never connects to the app? (In my tests, the app starts on the device, but VS never connects.)

    No, the app is not launched on the device

    Since weeks I’m also not able to debug to my iPhone 5:
    The app is deployed to the device and started, the I have a hard crash, whereby the error-message is related to Android
    I have filled a bug for this, almost a month ago:
    https://bugzilla.xamarin.com/show_bug.cgi?id=27776

    On Android-device (tablet and phone), I have similar problems (mostly, I can debug only one time to device, and further it is extremely slow (if the first breakpoint is reached, VS stops and show the line, the I have to wait minutes until the debugger is servable further).

    Further, in both IOS and Android, various objects are “unknown” = not observable (e.g. the application-object -> “Unknown identifier: Application” in debugger)
    I have filled a bug for this, more than two months ago:
    https://bugzilla.xamarin.com/show_bug.cgi?id=26492

    To be able to debug “a bit”, I have to change the platform/device by every debug-session (to be able to debug one time for each platform), then I have to restart VS. Actually, I am simply not able to debug my iPad and/or my iPhone.
    So, I have to “debug” blind without debugger (with DisplayAlerts or something similar) on the device
    Further I am not able to find out, where exactly a bug occurs / what exactly causes a crash and therefore I'am also not able to fill meaningful bugs to new XF-Version's (I normally overtakes the newest XF-versions to test it)

    Every debug session - if it then can be started - takes minutes until the debugger is available.
    Some of the objects can’t be observed, as they are “unknown”.

    :warning: Seriously, how should we work meaningful in this environment?!? :warning:

    Wednesday, April 1, 2015 8:09 AM
  • User118693 posted

    I am having problem mentioned earlier - VS gets stuck on "Launching application for debugging..." using the simulator. I am currently using version 3.9.483.0.

    It deploys succesfully to the simulator but no debugging

    Thursday, April 2, 2015 3:21 PM
  • User35081 posted

    I just found that i did not have to restart if i erased the contents of this directory every 20 min or so

    C:\Users\\AppData\Local\Xamarin\Log\12.0

    You can do this while VS is running.. Its keeping a WCF trace log of every call between PC and MAC.

    I also converted by C drive to a SSD.

    Thursday, April 2, 2015 5:23 PM
  • User3066 posted

    Same here! Stuck on "Launching Application for debugging" using 3.9.533. No errors, i just see Visual Studio debugger returning back to normal state, debugger probably gets detached under the hood.

    frustrating

    Sunday, April 5, 2015 7:56 AM
  • User3066 posted

    Did a connection test between VS and Mac machine and i see this error, I've just updated SDK and no request to sync SDK appears.

    Sunday, April 5, 2015 8:59 AM
  • User37800 posted

    Started getting this problem on iPAD emulator on Friday and today I updated packages and now it is also happening on the IPhone emulator, are there any known fixes for this ????

    Monday, April 13, 2015 8:06 PM
  • User106601 posted

    Same issue when debugging with iPad Air 2, Xamarin 3.9.547, Xmarin iOS 8.9.1.0, VS 2015. Using the emulator works fine..

    Tuesday, April 21, 2015 9:36 AM
  • User51906 posted

    @CorradoCavalli I found this bug today. If you're looking in the logs under %LOCALAPPDATA%/Xamarin/Logs in the newest log file you will be presented with this error:

    Xamarin.VisualStudio.IOS.BuildHost Warning: 0 : [2015-04-22 11:39:53.8] There is a minor mismatch between the installed Xamarin.iOS (version 8.10.0.258) on the Mac Build Host 192.168.111.101 and the local Xamarin.iOS 8.10.0.0. When applying updates, make sure to keep both the Mac and Windows in sync.

    After I found this error message I started investigating and what I found is really surprising to me^^ On my Build-Host Mac there is Xamarin.iOS 8.10.0.258 installed. On my PC there is Xamarin.iOS 8.10.0.0 installed. So the missmatch is from the .258 from the version number.

    Sadly though if I try to Sync them nothing happens. So no debugging or deploying to iOS anymore^^

    @BrendanZagaeski This should be easy to fix. I'm currently on Beta Channel.

    Wednesday, April 22, 2015 10:06 AM
  • User13824 posted

    Unfortunately, the "minor mismatch" warning in the log files is ignorable. As long as you have the Mac build host and the Windows machine updated to the same updater channel, they are properly synced. The SDK sync feature has been removed because new versions of Xamarin.iOS for Mac and Xamarin.iOS for Windows are now always released at the same time.

    Likewise, the last step in the build host diagnosis where it fails due to an "Outdated" SDK is ignorable. I've asked to have that step removed: https://bugzilla.xamarin.com/show_bug.cgi?id=28473.

    Wednesday, April 22, 2015 3:27 PM
  • User51906 posted

    The thing is, I'm on the same release channel. I'm gonna update now to the new Release 3.11.445 maybe it is working then.

    Thursday, April 23, 2015 6:38 AM
  • User51906 posted

    Works now :smile:

    Thursday, April 23, 2015 7:59 AM
  • User10694 posted

    I'm having the same problem since updating to Xamarin.iOs 8.10 and Xamarin 3.11.445. Tried to reboot Windows and Mac severall times but didn't help. Im running VS2012 on my Windows machine.

    Thursday, April 30, 2015 11:41 AM
  • User96711 posted

    I am facing the same problem with Visual Studio 2013. Xamarin.iOS 8.10 and Xamarin 3.11.445. All updated under stable channel. Please help @BrendanZagaeski . Could not debug on Mac through Build host showing Visual Studio Busy Notification while hanged.

    Monday, May 4, 2015 11:40 AM
  • User13824 posted

    One known cause of the issue in recent builds (anything more recent than 3.9.347) is https://bugzilla.xamarin.com/show_bug.cgi?id=28027. If (a) the app launches successfully on device, but (b) Visual Studio never shows any output from the application in "Output -> Debug" and (c) trying to stop debugging causes VS to hang, then you are most likely seeing bug 28027. In that case, feel free to add yourself on CC on the bug report, or if you have a Business or Enterprise license, feel free to contact support (if this link redirects to the top-level kb.xamarin.com/ page the first time you click it, try clicking it once more) to let us know, and we'll add you to the tally of affected customers.

    If the symptoms on bug 28027 do not match the issue you're seeing, the most direct way forward would be to file a bug report with as much detail as possible (if this link redirects to the top-level kb.xamarin.com/ page the first time you click it, try clicking it once more). Feel free to post the link to any new bug report back on this thread. Thanks!

    Monday, May 4, 2015 7:04 PM
  • User13824 posted

    Shoot. It turns out there is another cause of VS hangs when debugging iOS apps, this one specific to XamarinVS 3.11.445: Bug 29133. I had thought that bug was specific to Android, but I just confirmed that it also affects iOS. The "good" news for that bug is that it already has a fix and will be resolved in the upcoming service release (due to be released to the Alpha channel sometime this week).

    See the current release announcement for some additional details about both bug 28027 and bug 29133 (including how to request a "draft" development build that includes the fix for bug 29133).

    Monday, May 4, 2015 9:01 PM
  • User53480 posted

    Updating to the Alpha channel fixed the iOS debugging issue for me. Thanks!

    Thursday, May 7, 2015 6:35 PM
  • User115247 posted

    I also experienced this bug.

    VS2013 Xamarin 3.11.458

    I tried switching to the Alpha channel, but this did not resolve it :(

    Tuesday, June 2, 2015 8:04 AM
  • User138433 posted

    Keep getting this as well. Soooooo frustrating! Happens every not and then and at random so can't really give proper repo steps.

    Sunday, June 28, 2015 10:36 PM
  • User15498 posted

    Me too... WTF Xamarin guys, get your stuff stable! Literally every time I use your products, I go through this "Update to Latest Release / Reload / Deal With New Problem" cycle. SOO frustrated as a long-time paying customer.

    Sunday, July 12, 2015 5:48 AM
  • User116742 posted

    I'm experience this but on VS2015 but happends each 3 or 4 successfully deploy :sweat:

    Thursday, July 30, 2015 9:13 PM
  • User116742 posted

    Tried Alpha Release, and it got a bit better.. but the problem persist on VS 2015. Any solution to this already @BrendanZagaeski ?

    Friday, July 31, 2015 4:25 AM
  • User116742 posted

    I have noticed that If you disconnect your computer from WIFI (haven't tested on LAN) of the network you are connected with your build host, VS also hangs. I don't know if you already know this but I'm just putting that out there

    Friday, July 31, 2015 2:05 PM
  • User156380 posted

    Having the same issue on VS2015. Can deploy/debug to Android but deploying to connected iPhone hangs VS. (I also hang adding new resources through Visual Studio UI, so must edit csproj directly) -- perhaps weirdly related issues?

    Thursday, September 10, 2015 6:11 PM
  • User33845 posted

    This problem is still current.

    Interestingly, debugging works on an iPad3, but not on an iPhone 6+ (both with same provisioning profiles etc)

    Monday, October 5, 2015 3:12 PM
  • User140775 posted

    Same problem here. VS freezes for about 5 minutes, then says: There was an unhandled exception trying to deploy and run your application. Failed to start debug proxy on the Mac

    Wednesday, October 7, 2015 3:06 PM
  • User140775 posted

    :| Just switched over to the alpha channel. Is there no longer a Xamarin Build Host application? Because I now do not have one. Color me irritated.

    Wednesday, October 7, 2015 3:28 PM
  • User65389 posted

    @LeoArgyropoulos, @DebugErr, @MichaelArner.4520, @CarlosCamposSV and at all other readers if this thread: We all have the same problems... If you don't have seen it already, there is a brand new SW for the connection VS <-> MAC underway... I have gave up to hope for a stable VS integration software based on the actual as, it seems to be extremely buggy already in the base and the problems only are moved from one to anther over a full year now (and also the "terminator speak" ("I will be back...") to the evergreens (solved - reappears - solved - reappears) are extremely annoying (at least for me :smirk:)

    But the new IS-SW seems to be re-developed from ground so we all can hope, that the problems we all have, really are solved in the new version and the terminator then don't speak anymore!

    Therefore, I have opened a new thread here (where the users, that have done a test should post their findings): http://forums.xamarin.com/discussion/52913/new-visual-studio-ios-support-blog-your-findings#latest

    Unfortunately, the first version seems to work only with an English-Language installation...

    I suggest you, to keep an eye on the thread above... and let's hope that soon a user is able to check-out the new version and... only can post good things.... (as we all know... the hope dies last...)

    Or... better... maybe you have an English installation, want to test the new version and then post your findings in the other thread...? :wink:

    Cheers :sunglasses:

    Wednesday, October 7, 2015 3:32 PM
  • User33845 posted

    Yeah, I had similar thoughts. I couldn't install the 4.0 Alpha, my system is sadly German, and the MSI crashes...

    Wednesday, October 7, 2015 3:37 PM
  • User79866 posted

    I gave up on Visual Studio integration and now just use my Mac with Xamarin Studio. When my business license expires I will switch to Indie since this is the ONLY reason I purchased the business license. I am tempted to just bite the bullet and learn objective-C and just use XCode.

    Wednesday, October 7, 2015 3:54 PM
  • User161480 posted

    Same problem here, but only with an iOS on device (iPhone 5 with iOs 9)

    Working great with the iPhone simulator, Windows Phone simulator and on Nexus 7 device

    Visual Studio 2015 Windows 10 Everything update on MAC.

    Monday, October 19, 2015 5:43 PM
  • User55060 posted

    Same issues here. I can debug using the build host emulator on my Mac but can't use my physical iPhone. VS just hangs and says "Launching Application for debugging..."

    Monday, October 19, 2015 7:12 PM
  • User117939 posted

    I'm also experiencing this problem with problem. Unable to my device. VS hangs on "Launching Application for Debugging"

    Visual Studio 2013 Windows 8.1 Xamarin.iOS 9.0.1.29 OS 10.10

    Thursday, October 22, 2015 2:51 PM
  • User13824 posted

    Note that as Fredy mentioned, the Cycle 6 "Release Candidate" that is currently available on the Alpha updater channel includes a completely re-written build host (based on SSH rather than HTTPS). The new connection solves at least 2 specific timing-dependent problems that can arise when debugging on iOS simulators and devices on the current Stable version:

    1. The primary symptom on Bug 28027 where the VS debugger intermittently failed to connect to the device.
    2. A secondary problem where an immediate failure could happen if you attempted 2 deployments in rapid succession.

    It likely also fixes several other similar timing-dependent problems.

    Remaining hangs in the Cycle 6 Release Candidate

    If you still see hangs on the new Cycle 6 version, please do file a quick bug report using the Cycle 6 Release Candidate bug filing page. The XamarinVS team is quite interested to gather reports of symptoms in the Cycle 6 build host connection, even if the bug reports are "rough" (that is, even if they don't include all of the possible details or a specific way to reproduce the problem). Since the SSH-based connection code is still brand new, they are looking to get as much real-world usage data as possible to help make the eventual Stable version as robust as possible. Thanks in advance!

    Future reports of hangs after Cycle 6 is released to Stable

    I will now close this thread because reports of hangs in the IDE should almost always be directed to bug reports or emails to the support team via "Business & Enterprise Support." (Note that hangs in the IDE are always worthy of bug reports. Forum threads might occasionally be helpful for IDE hangs if other users have found some ways to work around the problem, but especially in cases like this thread where no workarounds have been found, bug reports are the best way forward. That said, I am happy to reopen this thread within the next month or two if a user does find a workaround they would like to share. Feel free to send a quick email to contact@xamarin.com to make that request.)

    If the problem resurfaces after Cycle 6 is released to Stable (or on any follow-up bugfix "Service Release" based on Cycle 6), please do file a bug using the specific bug-filing links that will be provided for those releases. Thanks again!

    Thursday, October 22, 2015 5:24 PM