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.
## Steps to reproduce
1. Create a new iOS project from Visual Studio
2. Enable IPA generation for Release configuration
3. Start a new Release build
## Expected behavior
Output path on the OSX box should still be the same as previous Xamarin versions: ~/Library/Caches/Xamarin/mtbs/builds/MyProjectWithoutDots/ProjectGUID/bin/iPhone/Release
## Actual Behavior
Since Xamarin VS 4.2, output path on the OSX box has changed to include back dots: ~/Library/Caches/Xamarin/mtbs/builds/My.Project.With.Dots/ProjectGUID/bin/iPhone/Release
Microsoft Visual Studio Enterprise 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Xamarin 184.108.40.2060 (c4382f5)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin Inspector Support 0.9.0.14 (4d868da)
Adds support for inspecting Xamarin and WPF apps.
Xamarin.Android 220.127.116.11 (0e59c36)
Visual Studio extension to enable development for Xamarin.Android.
Xamarin.iOS 10.0.0.6 (6c3fee4)
Visual Studio extension to enable development for Xamarin.iOS.
Those dots where removed nearly 2 years ago, which broke our CI at that time. Now those dots are back, which again broke our CI.
Last update (Xamarin VS 4.0/4.1) also introduced same kind of breaking changes with a new timestamped drop folder (and then a new way to fix it).
Those are little changes and relatively easy to handle once you know about them but:
- They induce work on CI where this is definitively something we have not. Once it works, we expect it to be reliable and not lose a day in useless fixes then testing.
- They are badly documented and most of the time buried in the release notes. You simply end up in loosing time to test and understand what is going wrong.
Also, those dots are still removed in the executable, .app and .ipa. I am just hoping this is not also going to change in the future.
This bug report is not to again remove those dots (I really don't want to lose time with this thing again!), but to ask for stability and consistency between releases!
Perhaps those kind of changes could be kept for bigger releases which happen less often (at least a year or few) and inserted all at a time?
I'm very sorry for the inconvenience. Point taken. Perhaps having a Breaking changes dedicated section on the release notes / communications can also help?
We do try to avoid such changes in general, but there are some cases where the fix is needed. We'll try to find out the best way to make future breaking changes as visible and discoverable as possible to at least minimize the effort of understanding what's going on.