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.
As per the docs http://developer.apple.com/library/ios/#documentation/general/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW11
This appears to be a regression since 2.6.
We have a bunch of Info.plists out there all with a string array as the key. Apparently iOS accepts this as this does not cause issues on the emulator, device or with app submissions. If it did, we would've found out by now.
If iOS does really accept this, there's probably no point in writing another monotouch project migrator to fix everyones info.plists. Nor is there any point in putting a hack to rewrite that section if a PListArray<string> is found instead of a PListArray<int>.
As such, i think the simplest solution is to just alter the section of code which creates the string array to instead create an int array and leave it at that. Does this sound reasonable?
Yup, that makes sense to me. It's not breaking anything but it's not as per the docs.
We parse both Array<string> and Array<int> now but only generate Array<int>. I also updated the templates to use <integer> instead of <string> which matches what Xcode generates.