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 for Bug 60974 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
There are some cases like this where hard references are required to pass Apple validation:
and a number (like the QTKit issues) where references are forbidden to pass Apple validation.
We should add a feature to mmp to allow customization of this. Something like:
which overrides the logic here:
Also, a few cases like MapKit could be handled if we parsed the info.plist.
I'm really sorry. I don't use Bugzilla as support but since I detect a bug, I post the bug via this subsidiary.
Normally, I don't need an immediate answer but here it's really very annoying because I can't post my application now.
Moreover, I don't understand because the solution you gave me a month ago to work and now more. As I said, the only difference is that I was in Xamarin.Mac 3.8 instead of 4.0. Can this be the problem ?
Can I get back to 3.8 without this being a problem in my application ?
Do I have to remove Maps to post my app now ?
Thanks for your help
@Alain as long as you are not using any new APIs added in XM 4.0 (High Sierra APIs) there should be no problem with going back to XM 3.8 until we can fix whatever is causing the problem.