Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
till today i could debug and run my application through the iPhone simulator, however after the latest update today from xamarin the project builds successfully says that the debugger is connecting to the iPhone simulator then it bombs out with no errors.
i have tried reinstalling tamarin, reinstalling revision profiles, restarting... nothing seems to work
even changed idk to 10 or default on the build options
Please help! this is really frustrating and i have tight deadlines!
To help the Xamarin team address this issue as efficiently as possible, please provide additional information, such as:
- Do you get the same problem on a new template iOS "Single View App"?
- Include the full log context for the behavior you are seeing. In this case, please collect the IDE log files from Xamarin Studio ("Help > Open Log Directory") or Visual Studio ("Help > Xamarin > Zip Logs") depending on which one you are using.
- Describe the environment where the bug was encountered, including the operating system and versions of Xamarin and any dependencies. In particular please:
(a) If applicable, collect and attach back the detailed version information from Visual Studio on Windows from "Help > About Microsoft Visual Studio > Copy Info".
(b) If applicable, please make a note of your Windows version too.
(c) Collect and attach back the detailed version information from Xamarin Studio on Mac from "Xamarin Studio > About Xamarin Studio > Show Details > Copy Information".
- If a new template project does _not_ show the problem, then if possible please attach a small, self-contained test case that reproduces the bug with as little code as possible.
See https://developer.xamarin.com/guides/cross-platform/troubleshooting/questions/howto-file-bug/ for additional details on what to include. Thanks in advance!
I have a similar problem. Since XS 6.1 and Xcode 8, my issue is if the simulator was already open before Xamarin Studio was started (mostly after a restart due to progressive slow-down), then it can't attach to the open simulator during debugging. I get this simulator error:-
"Error returned in reply: Connection invalid"
If the simulator is closed and the debugger restarted, then all is well.
I have managed to resolve this, but i would like the xamarin team to come up with a bug fix asap, the reason why the application wasn't running was cause of the latest Xcode 8 update which incorporates the iOS 10 and simulators for the new devices. Some how this update doesn't work with Xamarin since it has not catered for iOS 10. the only work around is currently to downgrade the Xcode version to 7 in order to run xamarin studio on mac.
I'm really frustrated with xamarin since you would expect them catering for the latest updates and not release unstable products out.
One small question, is your XS pointing to the appropriate Xcode version under the SDK settings? You need to point to Xcode8 in that section.
Yes - correct path to Xcode 8 for me
@Joseph, if you get a chance, if you would be able to file a new bug report that includes the information from Comment 1, that would be perfect. My concern is that the initial description in Comment 0 doesn't sound exactly like what you describe in Comment 2, so there could be separate issues involved.
Hello guys, is this still an issue?
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!