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.
Application Loader receives the error that the SDK version isn't supported when uploading the zip that is produced by MD's Zip App Bundle. I installed 2.6 beta3 and things worked there. However I suspect the Default.png file will not have uploaded (bug in beta3), but at least the application was able to be submitted using beta3, just not the trunk/stable MD.
I don't think this can be a bug in the zipping. it's most likely caused by missing or invalid keys in the compiled app's Info.plist. Did you try manually zipping the compiled app bundle?
Can you verify the version and build revision (in the about box) of the version of MonoDevelop that you're using? Vanilla 2.4.2 won't work, you need to make sure you have the latest hotfixed version of 2.4.2 from the MD updater.
The version of MD that gave me this error is 2.4.2. The Build Info is:
Release ID: 20402000
Git revision: d618bef0695ef150187dd2265a0f531f8c6d58b2
Build date: 2011-01-14 17:27:21+0000
I let the stable MD update itself, so I don't know if there was a hotfix applied or not, sorry I don't know how to verify that (build info perhaps?).
I do know that the beta 3 didn't have the problem and I haven't attempted with RC2 yet.
That's vanilla 2.4.2. If it's fixed in 2.6b3, it would also be fixed in the 2.4.2 hotfix available from the updater.
We should put the hotfix version up for download to replace vanilla 2.4.2