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 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.
Since xamarin.ios supports ios 8, when i compile and deploy my UITableView on a physical device in debug mode, the table cells are all superposed.
It works fine on the simulator in debug mode, and also works fine on the same device in release/adhoc mode.
Could it be that checksystemversion(8,0) may return true in that specific case ?
I forgot to write that the device uses ios 7.1
Calls to checksystemversion(8,0) should not return true on an iOS 7.1 device. We have several test applications that runs fine on older iOS release - so the constraints you have must be the reason.
OTOH the visual* behaviour for Debug and Release should be identical. Does the same issue happens on the simulator (compare debug vs release) ?
Can you attach a small, self contained, test case that reproduce the issue ?
* app size and performance can vary
note: we have seen many examples of constraints that worked fine on iOS7 but broke with iOS8. Sadly that's an Apple (iOS) issue that we can't work around (looks like they
Ok i found the issue.
In "properties", SDK version has been reset to 7.0.
This breaks UITables on ios8.
Setting it to 8.0 fixed the problem.
Note that the VisualStudio UI resets it to 7.0 each time you open the property panel, even if it is set to 8.0.
So if you change another setting and don't change the sdk version back to 8.0 you'll get problems as it will be saved as 7.0.
=> Visual Studio