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.
Licensing changes like this aren't going to make 2.0, too scary at this point in the game.
It appears you can work around this by turning on full linking, but that's not an idea work around.
And by full link, i mean don't link. ^
I have checked this issue with the latest master build XM 220.127.116.11 and I build the attached test sample and observed that I am successfully able to build the sample using "Indie" licence without showing any licence trigger window. Please refer the screencast for the same.
This issue has been fixed hence I am closing this issue.
Environment Info: https://gist.github.com/Rajneesh360Logica/4f86da54ac39f5f3f217
We have a customer reporting this. I'm going to have to dig and see what's going on.
Should be fixed by master / da39974bb612875ca7de8a030d66002ec9bd6021. Also in C6. I messaged the customer in question, and will have them try it out when it hits Alpha.