Bug 52552 - Allow using aars as references in binding projects
Summary: Allow using aars as references in binding projects
Status: RESOLVED DUPLICATE of bug 44573
Alias: None
Product: Android
Classification: Xamarin
Component: Bindings ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Atsushi Eno
Depends on:
Reported: 2017-02-15 23:09 UTC by Jeff Ward
Modified: 2017-06-26 17:12 UTC (History)
2 users (show)

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

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 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.

Related Links:

Description Jeff Ward 2017-02-15 23:09:46 UTC
We would like to be able to create a binding project that references, but does not create bindings for, a .aar.  This would basically be the same as the EmbeddedReferenceJar build action, except for aars instead (EmbeddedReferenceZip?).

In our praticular circumstance, we're creating a native library that abstracts several login providers, including twitter, and references the twitter aar. The C# code only uses our library, and therefore does not need to understand anything about the twitter aar.
Comment 1 Tom Opgenorth 2017-06-26 17:12:25 UTC
This sounds, fundamentally, the same issue as what was reported in https://bugzilla.xamarin.com/show_bug.cgi?id=44573.

*** This bug has been marked as a duplicate of bug 44573 ***