Roberto Leinardi05/14/2022, 10:11 PM
. The crazy thing is that the the enum on the same package is perfectly fine. And so is the AAR of the classic view library. And of course the issue does not happen if I import the gradle module directly instead of using the AAR. Do I need to do something special to generate an AAR with Composable? build.gradle of the library module
tad05/14/2022, 10:31 PM
files are just the top-level declarations from the .kt file, not the classes that are missing from that import list.
Roberto Leinardi05/14/2022, 10:33 PM
tad05/14/2022, 10:35 PM
Roberto Leinardi05/14/2022, 10:37 PM
tad05/14/2022, 10:47 PM
for a library project; usually you specify a
and let the consuming application set the target, otherwise there are some arcane rules used by the manifest merger
which would probably explain why the top-level functions aren't being resolved
and only add what's necessary to get the project to build
Leland Richardson [G]05/14/2022, 11:30 PM
Albert Chang05/15/2022, 3:12 AM
from the aar. That file is needed to access top-level members.
Roberto Leinardi05/15/2022, 8:06 AM
exclusion list was causing the problem! I don't remember from where I took that list but it never occurred that could have these side effects on AAR (I'm using it for months on a couple of apps without issue). But yeah, from now on I'll drop it and just manually add only what's needed. Thanks a lot!