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.
Scenario (which needs an actual testcase):
1. Binding Project B generates B.dll to bind B.jar
2. Library Project L references and uses Project B.
3. Application Project A references Project L, but NOT Project B.
4. Build and run.
Expected behavior: B.jar should be compiled into the Application.
Actual results: B.jar is NOT compiled into the application, resulting in java.lang.NoClassDefFoundErrors at runtime.
Created attachment 5979 [details]
Attached sample project Scratch.Bxc16589.zip.
Build, and it fails:
> obj/Debug/android/src/mono/com/xamarin/android/DataListenerImplementor.java(8,22): error : package com.xamarin.android does not exist
Edit the Scratch.Bxc16589 project references so that it also references the XamTestBinding project, and it builds successfully.
As Dean pointed out on IRC, XamarinVS had similar issues and the fix was to nuke their custom resolve code and just rely on the framework to do the right thing (which it does).
Why is it not sufficient to just invoke ResolveAssemblies like a regular build does and retrieve the list of all Nth order dependencies that way?
Now we have fix for custom _AndroidResolveAssemblyReferences issue. However this issue still persists for some reason. Maybe we have to change used items or properties to appropriate ones or add more target dependencies.
[master 01cb485, 9e1e1ec]
The assembly resolution issue for this particular bug is now also fixed.
I have checked this issue with the sample project attached into comment 3, and it is working fine, it build solution successfully. Hence, I am closing this issue.
Mac OS X 10.9.2
Xamarin Studio: 4.2.3 (build 60)
Xamarin.Android: 4.13.0 (Enterprise Edition)