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.
I'll let BB explain the details.
I tried to reproduce this issue but unable to reproduce this issue.
Could you please provide sample application or steps to reproduce this issue? So the we can reproduce this issue at our end.
This forum post has further details:
Forum post is specifically about Android I believe.
For me creating a new project thismorning allowed breakpointing. I also noticed new projects Debug|iPhone linker setting was SDK Assemblies only. Not sure if that is usually that by default but changing it around did not seem to help.
Two of my existing projects however, app just closes when it hits a breakpoint.
is a forum post that I put my crashlog in if that helps at all.
Could you attach the project which exhibits the problem or a small testcase ?
Turns out removing TestFlight from my app (not just the TestFlight.SetReportCrashes(true); line, but the TestFlight.TakeOff("key"); in particular).
Can repeat it again and again by uncommenting that one line and readding it. Don't think I had this issue in the past, seems to be new to iOS8. Have been using TestFlight 3.0.2 SDK for quite a while now, but was very recent this issue had started happening.
Its possible that TestFlight is interfering with the debugger, since the two use similar os fuctionality.
We have not received a test case. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!