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.
Steps to reproduce this issue:
1. Open or create iOS project.
2. Add iOS library to this solution.
3. Add library reference to the main iOS project.
Actual result: Trigger popup does not appear if user add library reference to main iOS project.
Expected Result: Trigger poup should appear if user add library reference to main iOS project.
X.S 4.0.5 (build4)
Mono 3.0.11 ((no/edc181c)
Moving: Those steps occurs inside XS only
what trigger popup? I'm not sure what is being described.
Heyo Nischal - so the behavior here is:
"On adding a native LinkWith reference [Starter = UPGRADE] [Indie, Trial, Standard, Priority = No behavior]"
This test case requires you to add a library project with LinkWith, probably from the monotouch-bindings repo.
People have been using something from monotouch-bindings for this. Please update the test case so it is is consistently run,
PJ, I have downloaded monotouch-bindings from https://github.com/mono/monotouch-bindings but I am not sure which library(which have LinkWith) I should add in my template project so that i can get check this behavior. Please provide me some steps.
Lal has executed the case successfully - he will make sure to propagate the information and clarify the case where there are points of confusion.
I did not want to specify any particular library in the case because we might as well get ancillary testing on various bindings (that don't otherwise get tested very much).
Sorry for the confusion, hopefully it's all sorted now.