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.