IssueTracker

This version which i am testing is the latest one : 2.0.8-dev

If you have the class in base, you don't need it in your feature!
also, can you be more specific, is the class exactly the same? Is is just named the same? (if so, use a different namespace)

Yes, but in my base module the library which i use is configured via "api" not "implementation" because i use it in other feature module
It was working ok before e.g in R8 version 2.0.2-dev

Please look at the stacktrace attached below.

To make it easier to figure our, can you bisect (i.e., exactly what version of R8 did this start failing in (i.e., which of 2.0.3-dev, 2.0.4-dev, 2.0.5-dev,2.0.6-dev 2.0.7-dev)
Also, just to be sure, you don't have the dependency in your feature as well?

Yes, i am sure that i don't have the dependency in my other feature modules, but they have an dependency of base module :

E.g :
Base module : api ':testLibrary:1.0.0'
Feature module : implementation project(':app') --- where "app" is the base module

About in which version it is start failing, just please wait some time to download and test them all while it will fail and will report back here.

Hmmmm....

I tried 2.0.4-dev, 2.0.3-dev and they fail. For being sure i test again 2.0.2-dev (which i said was working OK) but it fails again.

They only change that i have made since it not failing was upgrading AS from 4.0 Canary 4 to 4.0 Canary 5...

Maybe the new AGP (4.0.0-alpha05) is not instructing the R8 correctly or something wrong while merging/packing classes with complicated dependency ?

But it is still crash of R8 as you can see from the stacktrace in the comment #4

Over to Scott to answer that, cc Ivan

Can you please take a look at this other bug which i have reported in same time today just to know that it may be related to this one ?

https://issuetracker.google.com/issues/145684729

Just to add some more detailed info, the lib which is causing the R8 issue is added as .aar file in speilcific lib folder, and added via "api" in build.gradle of base module.

Thanks, I'm able to reproduce the issue, looking into it...

Ok, that's great. Please let me know when you will fix it and send here the custom version after commit, to use it immediately.
Thank you

There is an issue here even when not doing code shrinking.

The classes *and* resources from the local AAR dependency are being packaged in the dynamic feature APK *and* the base APK, and it's happening even if the local AAR dependency uses "implementation" instead of "api".

I've attached a repro project, which is just a project with the following structure:
dynamicfeature -> app -> lib1.aar

Running assembleDebug or assembleRelease and then examining the dynamicfeature and app APKs shows that lib1.aar's classes and resources are being packaged in both APKs, which isn't the case for 4.0.0-alpha04.

I haven't figured out why this is happening yet, but it seems the local AARs artifacts are being included in the dynamic feature's runtime dependencies, even though they shouldn't be.

Awesome, thanks Scott
re #12: just for clarity, this is not in R8, this is in the android gradle plugin. I am not sure that there is an easy way of getting a custom new version (as easy as R8 that is)

I understand. So will wait for next release. Unfortunately i will not be able to generate release app till next canary(maybe 2 weeks) ?

Just downgrade to an older version?
https://developer.android.com/studio/archive

Alternatively, just downgrade the android gradle plugin by explicitly setting it to the previous version
 classpath 'com.android.tools.build:gradle:4.0.0-alpha04
instead of
 classpath 'com.android.tools.build:gradle:4.0.0-alpha05

comment#16, yes this is what i did. I was sleepy when writing comment#15 :D :D and this change seems that solves this bug : https://issuetracker.google.com/issues/145684729

#17: Thanks for validating, keeping this open for Scott's investigation

This has been fixed. The fix will be included in 4.0.0-alpha07.

Change-Id: I1435497a7bb6d34373f17bd38d8ab6b5ce89a07e

Thank you for information. Will wait for it.
Best Regards

It is fixed on Canary 7 ! :) Thanks guys