Skip to content
This repository was archived by the owner on Apr 19, 2018. It is now read-only.

Add empty <application /> element to avoid a Gradle manifest merging error.#64

Open
barbeau wants to merge 1 commit intoJakeWharton:masterfrom
barbeau:patch-1
Open

Add empty <application /> element to avoid a Gradle manifest merging error.#64
barbeau wants to merge 1 commit intoJakeWharton:masterfrom
barbeau:patch-1

Conversation

@barbeau
Copy link

@barbeau barbeau commented Dec 19, 2013

Per Android Team (http://stackoverflow.com/a/17757200/937715), library manifests should include an empty <application /> element. Otherwise, the application cannot use a targetSdkVersion number that is different than the library when using Gradle/Android Studio. If the app uses a different targetSdkVersion, you get a compile error Manifest merging failed. - Main manifest has <uses-sdk android:targetSdkVersion='8'> but library uses targetSdkVersion='19'.

Per Android Team (http://stackoverflow.com/a/17757200/937715), library manifests should include an empty `<application />` element.  Otherwise, the application cannot use a targetSdkVersion number that is different than the library when using Gradle/Android Studio.  If the app uses a different targetSdkVersion, you get a compile error `Manifest merging failed. - Main manifest has <uses-sdk android:targetSdkVersion='8'> but library uses targetSdkVersion='19'`.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant