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.
See bug #56498 for a test case.
Code sharing is always beneficial, so we should allow code sharing if assemblies are found in different paths, but a byte-by-byte comparison reveals they're in fact identical.
This sounds like something that would be nice to get in 15.3, so I'm setting milestone accordingly.
*** Bug 56742 has been marked as a duplicate of this bug. ***
@Rolf Will this be in 15.3?
@kyle It is my understanding that because the change made it into master, it will be a part of the next Xamarin.iOS release which should be in a branch called d15-3. You can learn more here: https://github.com/xamarin/xamarin-macios/wiki
Yes, it will be in 15.3
To verify the bug I performed below steps :
1. Following bug-Bug 56742 I Downloaded a project: https://github.com/zippo227/ios-samples/tree/master/ios10/MessageCodeSharing
2. Launched VSFM
3. Opened project in VSFM
4. Build project
5. Observed the generated diagnostic logs
Actual Result- "Native code sharing has been disabled" is not displayed in the logs.
Is it the expected result?
Diagnostic Build Logs Link- https://gist.github.com/gangrade-swati/c1cc6d4bedd70bce54c3ea8d73484ed6
@Rolf Bjarne Kvinge Can you please confirm about verification steps an actual result. If all is good then I moved it to Verified state
@Swati, yes, that looks good.
So actual result and expected results are matched so shall I marked bug as verified?
Yes, consider this verified.