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.
I am trying to bind some Jars into my MonoDroid project.
I have succesfully managed to build the Java Binding Library so far, but when I reference the project from the Application Project, the Java Binding Library gets ignored because it cant bind Mono.Android.
I found that the Java Binding Library references Mono.Android 22.214.171.124, while the main project uses Mono.Android 126.96.36.199, I dont know if this could be an issue.
The picture in the link shows the assembly browser. It says that the assebly Mono.Android could not be loaded.
The same goes for Xamarin.Mobile.dll, in Mono for Android it gets ignored because it cant load Mono.Android.
The URL seems to be invalid... you should be able to reference 2.2 Mono.Android.dll from 2.3 project. I'm not sure what you mean by "Java Binding Library ... can't bind Mono.Android" (because Java binding library is to bind jars to a dll, not dlls to a dll). Could you give us an example? Thanks.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.