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.
When setting a TableView's Content Property from Dynamic Prototypes to Static Cells a very nondescript build error is present:
1>C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(997,3): error :
Changing it back to Dynamic, it builds with no errors.
Drag a View Controller onto the storyboard, then drag a Table View onto the controller. Set the Table View's Content property from Dynamic Prototypes to Static Cells and Build the solution.
Visual Studio Professional 2015
Xamarin for Windows 220.127.116.119 (f860fe4)
Xamarin.iOS 18.104.22.168 (3c0ec35)
OS X 10.11.1
Xamarin Studio 5.10 (build 871)
Both the errors and warnings from ibtool are being ignored when compiling interface definition files. Example output which gives no MSBuild errors or warnings: https://gist.github.com/alanmcgovern/5bf873fb06385045cdd3
Wayne, the error you were supposed to see was `Static table views are only valid when embedded in UITableViewController instances`, so the problem you had was just you were doing something iOS does not support. As such, i reassigned this to the iOS team so they can figure out why the error messages are not being reported correctly.
Hi Alan, Thanks much appreciated!
The problem is that we're in a situation where if we show errors reported by ibtool's stderr, we get bug #33706.
If we ignore stderr, we get this bug.
Rock. Hard place.
The errors aren't in stderr, they're in the manifest produced by ibtool when it finishes. I believe the issue is that if ibtool returns a non zero exit code we bail out before parsing and propagating the errors in that manifest
Or at least that's what I remember from looking into it last week :)
*** Bug 36410 has been marked as a duplicate of this bug. ***
oh, okay. Then that sounds more fixable.
Fixed in git master.