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 for Bug 35488 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 13627 [details]
On of the customers is working on porting an existing Android Java app (and libraries) to Xamarin.Android. They setup bindings projects around their Android Library AAR files and the app is working correctly with these. The problem arises when they want to make a change to the Java code and regenerate the bindings.
1. Make change to our Java project (e.g. add new public variable to a class)
2. Build the updated AAR which is referenced as LibraryProjectZip by our Xamarin bindings project
3. Build the bindings project in Xamarin Studio (only build - not rebuild)
4. View the generated bindings via assembly browser and notice our change is not there
In step #3, do a clean+build instead of just build, then notice the update propagates.
When we try to just 'build' then notice this in the build output:
Skipping target "GenerateBindings" because its outputs are up-to-date.
I'm also seeing this issue.