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.
When using the project properties editor in VS (2015) to configure the 'Main Interface' the Info.plist `LaunchScreen` attribute is generated with the file extension .storyboard. When verifying the compiled app via the Application Loader the error `ITMS-90096` is shown as the app is targeting 8.0> meaning slash-screen images are not required, only the storyboard (which is not found).
Manually removing the file extension from the Info.plist resolves the app validation error but editing other settings through VS regenerates the file extension.
We're reworking most of our Property Pages and fixing errors like this one.
But that work is targeted for cycle 10, which is not yet a public release.
Also, in cycle9 (version 4.3) you have a new PList Generic Editor, which allows you to edit the .plist file directly, not using the property pages, in case that helps.
I'm moving this bug to `cycle10` so we can ensure it's fixed as part of that effort.
Fixed on Xamarin for VS 220.127.116.117
Hi @Anthony Halliday, It will be great if you can provide steps to verify this bug.
Hello @Alok Kulkarni, after updating to the latest stable release of Xamarin for VS 2015 I can no longer reproduce the original issue where the `.storyboard` extension is generated.
This should most likely have its own issue but perhaps it is already being worked on with the above changes or I am misunderstanding something:
Since deploying the first version of our Xamarin app the iOS application loader has thrown an error when a reference to an app icon with the size `167` was not present.
When I first got the error I simply added the reference directly to the plist and the publish worked as expected. However when any member of the team modifies settings the the VS project properties window, e.g. build number, the `CFBundleIconFiles` value `Icon-167.png` is auto removed.
As per comment 4 the issue is no longer reproduced, hence marked as verified.