Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.
Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.
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.
Over the years multiple people have been bitten by the "fun" bug of the Apple installer: If you have a App NEXT TO the pkg when you install, it will for some crazy reason install on top of the app and not in application. Do a clean, move the pkg somewhere else, and try running it again. The user here suggested moving it to a sub folder on output. https://forums.xamarin.com/discussion/94361/installer-updater That seems like a reasonable suggestion, but I'm currently unsure if it is a safe non-breaking change. Research on if moving output files is considered breaking will be needed.
This will break customers who rely on the current location in things like CI build systems :\
Then likely it's a no-go IMO :(