Bug 35488 - Android library bindings project not detecting AAR changes
Summary: Android library bindings project not detecting AAR changes
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2015-11-03 03:43 UTC by Prashant Cholachagudda
Modified: 2017-07-06 08:08 UTC (History)
4 users (show)

Tags: ac
Is this bug a regression?: ---
Last known good build:

Logs (16.45 KB, application/zip)
2015-11-03 03:43 UTC, Prashant Cholachagudda

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Prashant Cholachagudda 2015-11-03 03:43:07 UTC
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.

Desired process:

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.

Other notes:
When we try to just 'build' then notice this in the build output:

Target GenerateBindings:
Skipping target "GenerateBindings" because its outputs are up-to-date.
Comment 1 wyattjoe40 2017-01-24 21:24:35 UTC
I'm also seeing this issue.