Android Gradle Plugin 1.4.0 betas up through beta 4 appear to improperly package .so files included in AAR files [37064125]

Fixed

Bug

[AOSP] FutureRelease

Migrated-Tools-Gradle

Status Update

No update yet.

Description

tb...@gmail.com

created issue #1

Oct 2, 2015 03:41AM

See this github project for full details:

https://github.com/tbsandee/RealmSoFailure

It appears to be a regression, because changing the plugin version to 1.3.1 fixes the issue.

Comments

em...@gmail.com <em...@gmail.com> #2Oct 2, 2015 05:38AM

can you share your android studio version

xa...@android.com <xa...@android.com> Oct 2, 2015 06:43AM

Assigned to xa...@android.com.

pi...@gmail.com <pi...@gmail.com> #3Oct 5, 2015 06:56AM

Is this happening with Studio 3.0?

pi...@gmail.com <pi...@gmail.com> #4Oct 5, 2015 07:00AM

Note: This worked for me on Windows 7 Pro 32-bit (with Android Studio 2.3.3). Seems like an issue with adt-branding module (which should contain the "/idea/AndroidStudioApplicationInfo.xml" resource).

tb...@gmail.com <tb...@gmail.com> #5Oct 5, 2015 02:31PM

Hi, also happened on Mac Book Pro 15 retina mi-2015
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

[Deleted User] <[Deleted User]> #6Oct 5, 2015 02:38PM

Thank you for this feedback. Your feedback helps make sure Android development tools are great! Given your issues has been resolved I am closing this issue.

fr...@gmail.com <fr...@gmail.com> #7Oct 7, 2015 01:29AM

The issue still exists on the latest beta6. Just chiming in, we all know these things take time to figure out.

[Deleted User] <[Deleted User]> #8Oct 15, 2015 06:39PM

The issue is still here indeed. It is annoying when you want to use the new features from gradle plug-in 1.4 like vector drawables.

[Deleted User] <[Deleted User]> #9Oct 15, 2015 10:53PM

This issue can also be reproduced if Databinding 1.0-rc3 is added to the project. 1.0-rc2 and plugin 1.3.1 does not have this issue.

xa...@android.com <xa...@android.com> #10Nov 4, 2015 12:45AM

Marked as fixed.

Can you check with 1.5.0-beta1? we completely revamped this part. thanks.

pi...@gmail.com <pi...@gmail.com> #11Nov 4, 2015 07:20AM

Can't answer that question, because our app crashes immediately after start with some class not found exception, looking for a class from library from dependencies. Probably time for another bug report.

al...@gmail.com <al...@gmail.com> #12Nov 4, 2015 11:33AM

#10 > if the root cause was similar to

https://code.google.com/p/android/issues/detail?id=182061 or

https://code.google.com/p/android/issues/detail?id=191196 I can confirm 1.5.0-beta1 fixed it.

tb...@gmail.com <tb...@gmail.com> #13Nov 4, 2015 01:42PM

1.5.0-beta1 does fix the issue for me (reporter). Thank you.