-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove uses-sdk from AndroidManifest.xml #664
Conversation
since uses-sdk values are now superseded by Gradle files resolves apache#629
LGTM |
This PR removes the handling of the values/attributes that should not be used any more. Do we also have the part where the replacement is set in |
I just added the context to the description, hope it is clear enough now. |
So merging this will break the code without #655 being merged as well? |
Merging this should not break anything that is not already broken. There exists issue #508 since Gradle does not use the information from AndroidManifest.xml. So my idea is to fix it in multiple steps:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok.
Thanks @janpio for the quick review! |
Something went wrong. I discovered that a result of this change is that the APK is generated with a nonsense target SDK value. This is because while the existing Gradle scripts do supersede the minSdkValue from AndroidManifest.xml, it do not supersede the targetSdkValue from AndroidManifest.xml. I will raise a new issue to describe the problem and discuss alternative solutions really soon. My apologies. |
This reverts commit bb45f4f. Resolves apache#666
Revert "Remove uses-sdk from AndroidManifest.xml (#664)"
since uses-sdk values are now superseded by Gradle files
see #629
P.S. Changes should be merged as a squash merge.
P.P.S. Here is the context: