Mixing
How do you get compile time SDK compatibility warnings from Gradle?
Was recently doing a project and mid-way we had to lower the minimum supported SDK supported in the Android manifest. Some Android API's we use are not compatible the new lower minimum SDK. We only discovered these as run time crashes. Why wouldn't the Gradle and/or the Android IDE pick up these as warnings ? Normally, I see the warnings as I code it, but for code already written, I am not warned during compilation.
I would like to be able to re-compile my project, and get all the API warnings about the minimum supported SDK. I had done some research on Lint, and it testing with it, has not yielded any results beyond warning me about XML style incompatibilities. So, I can't seem to find it for Gradle, and Android IDE is not running through the existing code already written, and raising warnings. Is this possible ? If it is, can someone provide a solution.
android 
android-studio android-gradle gradlew android-compatibility asked Nov 19 '18 at 22:34
giuliogiulio
5,30884470
add a comment |
Was recently doing a project and mid-way we had to lower the minimum supported SDK supported in the Android manifest. Some Android API's we use are not compatible the new lower minimum SDK. We only discovered these as run time crashes. Why wouldn't the Gradle and/or the Android IDE pick up these as warnings ? Normally, I see the warnings as I code it, but for code already written, I am not warned during compilation.
I would like to be able to re-compile my project, and get all the API warnings about the minimum supported SDK. I had done some research on Lint, and it testing with it, has not yielded any results beyond warning me about XML style incompatibilities. So, I can't seem to find it for Gradle, and Android IDE is not running through the existing code already written, and raising warnings. Is this possible ? If it is, can someone provide a solution.
android android-studio android-gradle gradlew android-compatibility asked Nov 19 '18 at 22:34
giuliogiulio
5,30884470
1
Related: How to enable lint error in Android Studio for message “Call requires API level 21 (current min is 16)”?
– Morrison Chang
Nov 20 '18 at 0:23
@MorrisonChang that's helpful, but I need to tune it for noSuchMethod / unsupported method related crashes. Deprecated is ok so long as it's still supported by the min SDK.
– giulio
Nov 20 '18 at 0:55
Not sure if this answer to Android API level annotation for Android libraries is helpful. The prior link I provided has some approaches. You may want to update your question with what you've tried.
– Morrison Chang
Nov 20 '18 at 1:30
@MorrisonChang thanks. But that answer implies that I am inserting the required annotations when writing the code. My problem is that I started building the app, then a reduced min sdk was introduced, thereby making some api's invalid without any relevant annotations. The compiler is not picking it up and deprecation warnings are overkill. Looking for something very specific.
– giulio
Nov 20 '18 at 2:05
add a comment |
Was recently doing a project and mid-way we had to lower the minimum supported SDK supported in the Android manifest. Some Android API's we use are not compatible the new lower minimum SDK. We only discovered these as run time crashes. Why wouldn't the Gradle and/or the Android IDE pick up these as warnings ? Normally, I see the warnings as I code it, but for code already written, I am not warned during compilation.
I would like to be able to re-compile my project, and get all the API warnings about the minimum supported SDK. I had done some research on Lint, and it testing with it, has not yielded any results beyond warning me about XML style incompatibilities. So, I can't seem to find it for Gradle, and Android IDE is not running through the existing code already written, and raising warnings. Is this possible ? If it is, can someone provide a solution.
android android-studio android-gradle gradlew android-compatibility asked Nov 19 '18 at 22:34
giuliogiulio
5,30884470
Was recently doing a project and mid-way we had to lower the minimum supported SDK supported in the Android manifest. Some Android API's we use are not compatible the new lower minimum SDK. We only discovered these as run time crashes. Why wouldn't the Gradle and/or the Android IDE pick up these as warnings ? Normally, I see the warnings as I code it, but for code already written, I am not warned during compilation.
I would like to be able to re-compile my project, and get all the API warnings about the minimum supported SDK. I had done some research on Lint, and it testing with it, has not yielded any results beyond warning me about XML style incompatibilities. So, I can't seem to find it for Gradle, and Android IDE is not running through the existing code already written, and raising warnings. Is this possible ? If it is, can someone provide a solution.
android android-studio android-gradle gradlew android-compatibility android android-studio android-gradle gradlew android-compatibility asked Nov 19 '18 at 22:34
giuliogiulio
5,30884470
asked Nov 19 '18 at 22:34
giuliogiulio
5,30884470
edited Nov 19 '18 at 22:45
giulio
asked Nov 19 '18 at 22:34
giuliogiulio
5,30884470
asked Nov 19 '18 at 22:34
giuliogiulio
5,30884470
asked Nov 19 '18 at 22:34
giuliogiulio
5,30884470
5,30884470
1
Related: How to enable lint error in Android Studio for message “Call requires API level 21 (current min is 16)”?
– Morrison Chang
Nov 20 '18 at 0:23
@MorrisonChang that's helpful, but I need to tune it for noSuchMethod / unsupported method related crashes. Deprecated is ok so long as it's still supported by the min SDK.
– giulio
Nov 20 '18 at 0:55
Not sure if this answer to Android API level annotation for Android libraries is helpful. The prior link I provided has some approaches. You may want to update your question with what you've tried.
– Morrison Chang
Nov 20 '18 at 1:30
@MorrisonChang thanks. But that answer implies that I am inserting the required annotations when writing the code. My problem is that I started building the app, then a reduced min sdk was introduced, thereby making some api's invalid without any relevant annotations. The compiler is not picking it up and deprecation warnings are overkill. Looking for something very specific.
– giulio
Nov 20 '18 at 2:05
add a comment |
1
Related: How to enable lint error in Android Studio for message “Call requires API level 21 (current min is 16)”?
– Morrison Chang
Nov 20 '18 at 0:23
@MorrisonChang that's helpful, but I need to tune it for noSuchMethod / unsupported method related crashes. Deprecated is ok so long as it's still supported by the min SDK.
– giulio
Nov 20 '18 at 0:55
Not sure if this answer to Android API level annotation for Android libraries is helpful. The prior link I provided has some approaches. You may want to update your question with what you've tried.
– Morrison Chang
Nov 20 '18 at 1:30
@MorrisonChang thanks. But that answer implies that I am inserting the required annotations when writing the code. My problem is that I started building the app, then a reduced min sdk was introduced, thereby making some api's invalid without any relevant annotations. The compiler is not picking it up and deprecation warnings are overkill. Looking for something very specific.
– giulio
Nov 20 '18 at 2:05
1
1
Related: How to enable lint error in Android Studio for message “Call requires API level 21 (current min is 16)”?
– Morrison Chang
Nov 20 '18 at 0:23
Related: How to enable lint error in Android Studio for message “Call requires API level 21 (current min is 16)”?
– Morrison Chang
Nov 20 '18 at 0:23
@MorrisonChang that's helpful, but I need to tune it for noSuchMethod / unsupported method related crashes. Deprecated is ok so long as it's still supported by the min SDK.
– giulio
Nov 20 '18 at 0:55
@MorrisonChang that's helpful, but I need to tune it for noSuchMethod / unsupported method related crashes. Deprecated is ok so long as it's still supported by the min SDK.
– giulio
Nov 20 '18 at 0:55
Not sure if this answer to Android API level annotation for Android libraries is helpful. The prior link I provided has some approaches. You may want to update your question with what you've tried.
– Morrison Chang
Nov 20 '18 at 1:30
Not sure if this answer to Android API level annotation for Android libraries is helpful. The prior link I provided has some approaches. You may want to update your question with what you've tried.
– Morrison Chang
Nov 20 '18 at 1:30
@MorrisonChang thanks. But that answer implies that I am inserting the required annotations when writing the code. My problem is that I started building the app, then a reduced min sdk was introduced, thereby making some api's invalid without any relevant annotations. The compiler is not picking it up and deprecation warnings are overkill. Looking for something very specific.
– giulio
Nov 20 '18 at 2:05
@MorrisonChang thanks. But that answer implies that I am inserting the required annotations when writing the code. My problem is that I started building the app, then a reduced min sdk was introduced, thereby making some api's invalid without any relevant annotations. The compiler is not picking it up and deprecation warnings are overkill. Looking for something very specific.
– giulio
Nov 20 '18 at 2:05
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383612%2fhow-do-you-get-compile-time-sdk-compatibility-warnings-from-gradle%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383612%2fhow-do-you-get-compile-time-sdk-compatibility-warnings-from-gradle%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Related: How to enable lint error in Android Studio for message “Call requires API level 21 (current min is 16)”?
– Morrison Chang
Nov 20 '18 at 0:23
@MorrisonChang that's helpful, but I need to tune it for noSuchMethod / unsupported method related crashes. Deprecated is ok so long as it's still supported by the min SDK.
– giulio
Nov 20 '18 at 0:55
Not sure if this answer to Android API level annotation for Android libraries is helpful. The prior link I provided has some approaches. You may want to update your question with what you've tried.
– Morrison Chang
Nov 20 '18 at 1:30
@MorrisonChang thanks. But that answer implies that I am inserting the required annotations when writing the code. My problem is that I started building the app, then a reduced min sdk was introduced, thereby making some api's invalid without any relevant annotations. The compiler is not picking it up and deprecation warnings are overkill. Looking for something very specific.
– giulio
Nov 20 '18 at 2:05