MonoTouch debugger never connects to app

前端 未结 8 1278
野性不改
野性不改 2021-01-04 13:20

I have an issue where the MonoDevelop debugger refuses to connect to the simulator. MonoDevelop pops a box saying \"Waiting for debugger to connect on 127.0.0.1:10000...\" b

相关标签:
8条回答
  • 2021-01-04 13:33

    If you have a custom settings bundle then it will disable the debugger after a clean build. I filed this as a bug: https://bugzilla.xamarin.com/show_bug.cgi?id=3891

    As a workaround you can set the build action for your settings bundle's Root.plist to None then do a clean build. Once you've done that you can then reenable your Root.plist. It will merge your settings with the debug settings. That will work until you do a clean build again, at which point you will have to again disable your Root.plist and rebuild.

    0 讨论(0)
  • 2021-01-04 13:34

    Make sure you've got in project's oprions --> iPhone Build --> SDK Version set to default. On my machine anythings else causes simulator debugger to hang.

    0 讨论(0)
  • 2021-01-04 13:36

    I found that if you disable the linker, that often makes these kids of issues go away. Not sure how. alt text

    0 讨论(0)
  • 2021-01-04 13:38

    I was having the same problem and I'll share my solution in case anyone else made the same embarrassing mistake. I didn't have wifi enabled, so my iPhone didn't have a NAT address like 192.168.1.xxx, so it wasn't able to contact the NAT address that MonoDevelop was listening from.

    Enabling wifi and connecting to my home network fixed it.

    0 讨论(0)
  • 2021-01-04 13:38

    It could also depend from content files (files with Build Action = Content) added inside some particular directories: e.g. you cannot create a directory called 'Resources' and put a content file inside, MonoDevelop hangs saying "Waiting for debugger to connect...." instead of raising a meaningful error.

    See also this thread: http://forums.monotouch.net/yaf_postst361_Bug-or-Misunderstanding-Resource-Content--Black-Simulator-Screen.aspx

    0 讨论(0)
  • 2021-01-04 13:48

    Try the following:

    1. In the simulator, go to the Settings "app"
    2. Find your app's name in the list below General/Safari/Photos
    3. Tap it to bring up its settings
    4. You should be looking at your app's "Debug Settings"
    5. Is "Enabled" (the first item) set to "On" or "Off"?

    That's the first thing to look at. If your app's debug "Enabled" setting is "Off" when you try to debug your app, your app will load in the simulator, and MonoDevelop will say it's trying to connect (because it is), but it won't be able to, so... well, you'll get the results you're describing.

    If you go through the steps in that list and encounter any problems (like your app not showing up in the simulator's "Settings" list, or it not having "Debug Settings", or it still not working despite having switched "Enabled" to "On"), then you can try a few other things (in no particular order - just typing what comes to mind):

    • Create a new project from scratch. Does the same thing happen? That is, does this problem exist for all your apps?

    • In MonoDevelop, open your app's project settings, click on "iPhone Build", and, with the configuration set to "Debug" and the platform set to "iPhone Simulator", ensure that "Build debug-mode binaries" is checked.

    • In MonoDevelop, open the "Build" menu, select "Clean All", rebuild your project, and try again.

    • If your app is properly configured, and if its settings on the simulator are correct, then try debugging your app - if MonoDevelop still sits and tries to connect without success, open up a terminal window (while your app is still running) and type "netstat -n -f inet" - do you see "127.0.0.1:10000" anywhere in the list under the "Local Address" column? If not, then something's probably wonky on the simulator.

    • If nothing seems to be working, and if you've already reinstalled the MonoTouch stack (as it seems you have), you can try opening the iPhone simulator, open the "iPhone Simulator" menu, and click on "Reset Content and Settings..." - it can be an inconvenience, but if you're running out of options, you might as well give it a shot.

    Without knowing more about your setup or having access to log files, it's tough to figure out what's going on, but those are a few things I think are worth trying.

    Hope this helps - at least to point you in a useful direction :)

    0 讨论(0)
提交回复
热议问题