How to disable Android TV Support in my app? Manifest complaining about missing LEANBACK_LAUNCHER
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I've been searching for a way to disable Android TV Support from the manifest. I know our app is incompatible and I've read that even when you aim at supporting Android TV, apps turn out unsupported anyways.
However, I have not found a way to stop the Manifest from asking for a INTENTBACK_LAUNCHER. I don't want to define one because I know that our app is not compatible with TV.
These are the warnings that I get right now:
Expecting uses-feature android:name="android.software.leanback" android:required="false" tag.
Expecting an activity to have android.intent.category.LEANBACK_LAUNCHER intent filter.
Hardware feature android.hardware.touchscreen not explicitly marked as optional
So when I try to supply the expected tags, even if I say the following:
uses-feature android:name="android.hardware.touchscreen" android:required="true"
It still sends a warning that it might not be supported by all TVs, which is nothing else than a warning but really annoying because I deliberately don't want to support Android TV. And even after I still get the LEANBACK_LAUNCHER intent filter warning as well.
Wouldn't requiring a touchscreen rid me of the manifest asking for a LEANBACK_LAUNCHER? I guess some TVs have touchscreens?
Anybody knows how to explicitly disable Android TV Support?
Thank you,
android android-manifest android-tv disable
add a comment |
I've been searching for a way to disable Android TV Support from the manifest. I know our app is incompatible and I've read that even when you aim at supporting Android TV, apps turn out unsupported anyways.
However, I have not found a way to stop the Manifest from asking for a INTENTBACK_LAUNCHER. I don't want to define one because I know that our app is not compatible with TV.
These are the warnings that I get right now:
Expecting uses-feature android:name="android.software.leanback" android:required="false" tag.
Expecting an activity to have android.intent.category.LEANBACK_LAUNCHER intent filter.
Hardware feature android.hardware.touchscreen not explicitly marked as optional
So when I try to supply the expected tags, even if I say the following:
uses-feature android:name="android.hardware.touchscreen" android:required="true"
It still sends a warning that it might not be supported by all TVs, which is nothing else than a warning but really annoying because I deliberately don't want to support Android TV. And even after I still get the LEANBACK_LAUNCHER intent filter warning as well.
Wouldn't requiring a touchscreen rid me of the manifest asking for a LEANBACK_LAUNCHER? I guess some TVs have touchscreens?
Anybody knows how to explicitly disable Android TV Support?
Thank you,
android android-manifest android-tv disable
Do you happen to have abanner
attribute on the<application>
element in your manifest?
– Mike M.
Nov 16 '18 at 15:26
No. No banner attribute in application element, unfortunately.
– kriztho
Nov 28 '18 at 21:36
add a comment |
I've been searching for a way to disable Android TV Support from the manifest. I know our app is incompatible and I've read that even when you aim at supporting Android TV, apps turn out unsupported anyways.
However, I have not found a way to stop the Manifest from asking for a INTENTBACK_LAUNCHER. I don't want to define one because I know that our app is not compatible with TV.
These are the warnings that I get right now:
Expecting uses-feature android:name="android.software.leanback" android:required="false" tag.
Expecting an activity to have android.intent.category.LEANBACK_LAUNCHER intent filter.
Hardware feature android.hardware.touchscreen not explicitly marked as optional
So when I try to supply the expected tags, even if I say the following:
uses-feature android:name="android.hardware.touchscreen" android:required="true"
It still sends a warning that it might not be supported by all TVs, which is nothing else than a warning but really annoying because I deliberately don't want to support Android TV. And even after I still get the LEANBACK_LAUNCHER intent filter warning as well.
Wouldn't requiring a touchscreen rid me of the manifest asking for a LEANBACK_LAUNCHER? I guess some TVs have touchscreens?
Anybody knows how to explicitly disable Android TV Support?
Thank you,
android android-manifest android-tv disable
I've been searching for a way to disable Android TV Support from the manifest. I know our app is incompatible and I've read that even when you aim at supporting Android TV, apps turn out unsupported anyways.
However, I have not found a way to stop the Manifest from asking for a INTENTBACK_LAUNCHER. I don't want to define one because I know that our app is not compatible with TV.
These are the warnings that I get right now:
Expecting uses-feature android:name="android.software.leanback" android:required="false" tag.
Expecting an activity to have android.intent.category.LEANBACK_LAUNCHER intent filter.
Hardware feature android.hardware.touchscreen not explicitly marked as optional
So when I try to supply the expected tags, even if I say the following:
uses-feature android:name="android.hardware.touchscreen" android:required="true"
It still sends a warning that it might not be supported by all TVs, which is nothing else than a warning but really annoying because I deliberately don't want to support Android TV. And even after I still get the LEANBACK_LAUNCHER intent filter warning as well.
Wouldn't requiring a touchscreen rid me of the manifest asking for a LEANBACK_LAUNCHER? I guess some TVs have touchscreens?
Anybody knows how to explicitly disable Android TV Support?
Thank you,
android android-manifest android-tv disable
android android-manifest android-tv disable
asked Nov 16 '18 at 15:12
krizthokriztho
669
669
Do you happen to have abanner
attribute on the<application>
element in your manifest?
– Mike M.
Nov 16 '18 at 15:26
No. No banner attribute in application element, unfortunately.
– kriztho
Nov 28 '18 at 21:36
add a comment |
Do you happen to have abanner
attribute on the<application>
element in your manifest?
– Mike M.
Nov 16 '18 at 15:26
No. No banner attribute in application element, unfortunately.
– kriztho
Nov 28 '18 at 21:36
Do you happen to have a
banner
attribute on the <application>
element in your manifest?– Mike M.
Nov 16 '18 at 15:26
Do you happen to have a
banner
attribute on the <application>
element in your manifest?– Mike M.
Nov 16 '18 at 15:26
No. No banner attribute in application element, unfortunately.
– kriztho
Nov 28 '18 at 21:36
No. No banner attribute in application element, unfortunately.
– kriztho
Nov 28 '18 at 21:36
add a comment |
1 Answer
1
active
oldest
votes
You can disable the lint checks by adding the tools:ignore
attribute to your manifest as follows:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="com.example.sampleapp"
tools:ignore="ImpliedTouchscreenHardware,MissingLeanbackLauncher,MissingLeanbackSupport">
add a comment |
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%2f53340532%2fhow-to-disable-android-tv-support-in-my-app-manifest-complaining-about-missing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can disable the lint checks by adding the tools:ignore
attribute to your manifest as follows:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="com.example.sampleapp"
tools:ignore="ImpliedTouchscreenHardware,MissingLeanbackLauncher,MissingLeanbackSupport">
add a comment |
You can disable the lint checks by adding the tools:ignore
attribute to your manifest as follows:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="com.example.sampleapp"
tools:ignore="ImpliedTouchscreenHardware,MissingLeanbackLauncher,MissingLeanbackSupport">
add a comment |
You can disable the lint checks by adding the tools:ignore
attribute to your manifest as follows:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="com.example.sampleapp"
tools:ignore="ImpliedTouchscreenHardware,MissingLeanbackLauncher,MissingLeanbackSupport">
You can disable the lint checks by adding the tools:ignore
attribute to your manifest as follows:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="com.example.sampleapp"
tools:ignore="ImpliedTouchscreenHardware,MissingLeanbackLauncher,MissingLeanbackSupport">
answered Mar 29 at 10:52
user2019414user2019414
13
13
add a comment |
add a comment |
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%2f53340532%2fhow-to-disable-android-tv-support-in-my-app-manifest-complaining-about-missing%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
Do you happen to have a
banner
attribute on the<application>
element in your manifest?– Mike M.
Nov 16 '18 at 15:26
No. No banner attribute in application element, unfortunately.
– kriztho
Nov 28 '18 at 21:36