Package does not exist when using separate App as a dependency

Question

I'm trying to compile an App utilising a separate App as a dependency but when I compile referencing modules from this library I see several "error:package does not exist" and "error:cannot find symbol class" messages from graddle. The following are my two build files.

apply plugin: 'android'

android {
    compileSdkVersion 19
    buildToolsVersion "19.1.0"

    defaultConfig {
        minSdkVersion 11
        targetSdkVersion 19
    }

    buildTypes {
        release {
            runProguard false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
        }
    }

    packagingOptions {
        exclude 'AndroidManifest.xml'
        exclude 'resources.arsc'
        exclude 'classes.dex'
    }
}

dependencies {
    repositories {
        mavenCentral()
    }
    compile 'com.android.support:support-v4:+'
    compile 'com.google.code.gson:gson:2.2.2'
    compile 'com.google.android.gms:play-services:+'
    compile 'com.actionbarsherlock:actionbarsherlock:4.4.0@aar'
    compile 'com.android.support:support-v4:+'
    compile 'com.readystatesoftware.systembartint:systembartint:1.0.3'
    compile 'se.emilsjolander:stickylistheaders:2.+'
    compile 'com.googlecode.libphonenumber:libphonenumber:+'
    compile files('libs/crashlytics.jar')
    compile files('libs/httpclient-4.2.3.jar')
    compile files('libs/libphonenumber-5.9.jar')
    compile files('libs/mobileservices-0.2.0-javadoc.jar')
    compile files('libs/mobileservices-0.2.0.jar')
    compile files('libs/stringtotime-1.0.4.jar')
    compile files('libs/urbanairship-lib-2.0.2.jar')
    compile 'com.github.chrisbanes.actionbarpulltorefresh:extra-abs:+'
    compile files('libs/FlurryAnalytics-4.0.0.jar')
    compile 'com.squareup.picasso:picasso:2.3.3'
    compile project(':wheel')
}

Dependency gradle:

apply plugin: 'android'

android {
    compileSdkVersion 19
    buildToolsVersion "19.1.0"

    defaultConfig {
        applicationId "kankan.wheel"
        minSdkVersion 5
        targetSdkVersion 7
    }

    buildTypes {
        release {
            runProguard false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
        }
    }

}

Can anyone help/experienced this before? Android Studio does not highlight any issues in the class and I can ctrl+click through to the packages referenced which seems to mean it is set up correctly...

Thanks!

score 6 · Answer 1 · answered Aug 07 '16 at 14:39

6

The buildTypes section should not be in library build.gradle file.

answered Aug 07 '16 at 14:39

Vladimir Berezkin

3,580
4
27
33

1

I would +100 this if I could. Thanks. – Dariush Malek Apr 21 '17 at 11:04
1

Your suggestion worked for me however is there any explanation for it?? – Ritesh Gune Apr 26 '17 at 07:27

Doge · Accepted Answer · 2015-04-17T06:39:05.123

5

You cannot have two gradle scripts using the com.android.application plugin at the same time. Change the dependency project to apply the 'library' plugin.

If that doesn't do it, change the targetSdkVersion of your dependency to that of your core project.

edited Apr 17 '15 at 06:39

answered Sep 26 '14 at 00:37

Doge

6,553
5
24
25

@Doge You mean `com.android.application`? – IgorGanapolsky Apr 17 '15 at 05:28
Yes, this is the new plugin name. When I originally wrote the answer the plugin was named simply 'android' – Doge Apr 17 '15 at 06:38

score 1 · Answer 3 · answered Feb 15 '15 at 21:17

1

If you are using a Android library module as a dependency (i.e. mylib), then make sure in your app.iml file that you see the following line toward the end of the file:

    <orderEntry type="module" module-name="mylib" exported="" />

answered Feb 15 '15 at 21:17

Man Vs Code

1,058
10
14

score 0 · Answer 4 · answered Sep 26 '14 at 00:32

0

Try changing min and target sdk to 11 and 19 according in dependency gradle-default config.

answered Sep 26 '14 at 00:32

Mandav Prakash

29
7

score 0 · Answer 5 · edited May 23 '17 at 11:46

0

I had a similar issue posted here

But I got it resolved using @Doge's suggestion, I converted the dependency android project to library project.

Thanks.

edited May 23 '17 at 11:46

Community

1
1

answered Sep 27 '14 at 04:57

Vijay Rajanna

645
1
8
15

But this error occurs in the library module, not the app module. So why would it matter to convert your android project to library?? – IgorGanapolsky Apr 17 '15 at 05:34
Your link was removed – Native_Mobile_Arch_Dev Mar 20 '17 at 16:06

Package does not exist when using separate App as a dependency

5 Answers5

Linked