Android Studio dependencies of module not visible in other module

Question

I have a module called "Common" as library, this module has few dependencies like: com.badlogicgames.gdx, com.squareup.wire etc. And it works fine, I use them inside of this module.

And I have another module called "Tracking", where in the gradle I have:

dependencies {
  compile project(':Common')
}

And if I try there to import any public class of module "Common", it works fine, but if I try to import any class of library com.badlogicgames.gdxor com.squareup.wire, it says me "Cannot resolve symbol ..." and hightlight it red. And no code autocompleting for such classes.

However the project compiles and starts on the device without errors.

Has somebody any idea? I tried "clean and rebuild" for project, "invalidate cashes and restart" for Android Studio. Nothing helps.

You can refer this https://stackoverflow.com/questions/19067846/android-studio-not-showing-modules-in-project-structure/31509751 — basavaraj ganagi, Nov 22 '18 at 14:20
@basavarajganagi my Project Structure is ok, there are all modules and their dependencies. — Alexander Tumanin, Nov 22 '18 at 14:24

score 1 · Answer 1 · answered Nov 22 '18 at 14:20

in the module common you need to declare those transitive dependencies as api to expose them to other modules:

e.g. common/build.gradle:

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation 'com.android.support:appcompat-v7:28.0.0'
    api 'com.squareup.wire'
}

https://jeroenmols.com/blog/2017/06/14/androidstudio3/

Khemraj Sharma · Answer 2 · 2018-11-22T14:21:49.420

0

Solution

Change compile to api

dependencies {
  api project(':Common')
}

Reason

Because compile is deprecated, so it is been treated as implementation. FYI compile and api (new keyword for compile) are same in which all internal modules are visible. But new gradle project having compile keyword are treated as implementation. and in implementation internal modules are not visible to main project.

Suggestion

You should declare dependency in your gradle because it is not good to make leak of internal modules.

edited Nov 22 '18 at 14:21

answered Nov 22 '18 at 14:20

Khemraj Sharma

57,232
27
203
212

I use old gradle version `distributionUrl=../../../../androidGradleDistribution/gradle-3.3-all.zip` – Alexander Tumanin Nov 22 '18 at 14:21
What is keyword other module using for declaring `squareup.wire`? – Khemraj Sharma Nov 22 '18 at 14:24
`compile 'com.squareup.wire:wire-runtime:2.1.0'` – Alexander Tumanin Nov 22 '18 at 14:25
You must declare this dependency to your project too, perhaps this is AAR, which does not contain nested dependencies. – Khemraj Sharma Nov 22 '18 at 14:28
It means I will have the same library twice in the project and the size of project increases. Strange is the thing, that it worked in the past, but last few days I get this problem. – Alexander Tumanin Nov 22 '18 at 14:31
That will not be twice in your project if you use same version. – Khemraj Sharma Nov 22 '18 at 15:15
It's surely not a library issue, because I can run app and it works with theese "unvisible" classes well without exceptions. It means the library is there and can be used. – Alexander Tumanin Nov 23 '18 at 12:27

Android Studio dependencies of module not visible in other module

2 Answers2