Revoke permission from the permission list issue
After revoking permission from the permission list the app won't restart.
I read that after revoking permission from the list the app process been terminate.
Can anyone confirm this?
android android-studio android-activity
add a comment |
After revoking permission from the permission list the app won't restart.
I read that after revoking permission from the list the app process been terminate.
Can anyone confirm this?
android android-studio android-activity
Can anyone confirm this? - yes, you can. Revoke the permission and see what happens. It's not hard.
– Tim Castelijns
Nov 15 '18 at 9:54
It is possible to make the app restart after revoke permission by itself?
– Shalev Cohen
Nov 15 '18 at 9:56
add a comment |
After revoking permission from the permission list the app won't restart.
I read that after revoking permission from the list the app process been terminate.
Can anyone confirm this?
android android-studio android-activity
After revoking permission from the permission list the app won't restart.
I read that after revoking permission from the list the app process been terminate.
Can anyone confirm this?
android android-studio android-activity
android android-studio android-activity
edited Nov 15 '18 at 9:48
Vivek Mishra
3,93843257
3,93843257
asked Nov 15 '18 at 9:44
Shalev CohenShalev Cohen
11
11
Can anyone confirm this? - yes, you can. Revoke the permission and see what happens. It's not hard.
– Tim Castelijns
Nov 15 '18 at 9:54
It is possible to make the app restart after revoke permission by itself?
– Shalev Cohen
Nov 15 '18 at 9:56
add a comment |
Can anyone confirm this? - yes, you can. Revoke the permission and see what happens. It's not hard.
– Tim Castelijns
Nov 15 '18 at 9:54
It is possible to make the app restart after revoke permission by itself?
– Shalev Cohen
Nov 15 '18 at 9:56
Can anyone confirm this? - yes, you can. Revoke the permission and see what happens. It's not hard.
– Tim Castelijns
Nov 15 '18 at 9:54
Can anyone confirm this? - yes, you can. Revoke the permission and see what happens. It's not hard.
– Tim Castelijns
Nov 15 '18 at 9:54
It is possible to make the app restart after revoke permission by itself?
– Shalev Cohen
Nov 15 '18 at 9:56
It is possible to make the app restart after revoke permission by itself?
– Shalev Cohen
Nov 15 '18 at 9:56
add a comment |
1 Answer
1
active
oldest
votes
No, if you go to setting and revoke permissions of an app, the app just lost focus and also in background, you could see it in recent apps list.
When you finish revoking and return to the app, it comes to foreground and corresponding life cycle callback would be triggered. And if the app need these permissions to run, but which be revoked by user, the app should run abnormally!
That's incorrect. There may be a screenshot of the app in the recents list, but it's no longer running. You can see this e.g. by looking at the running activities withadb shell dumpsys activity activities
. Regarding "if the app need these permissions to run, but which be revoked by user, the app should run abnormally" - an app should never assume that it still has a permission just because the permission was granted at some point in the past. It should always request the necessary permission right before performing the action that requires the permission.
– Michael
Nov 15 '18 at 12:59
Yes, after android 6.0, we should request permissions explicitly.
– navylover
Nov 15 '18 at 13:36
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%2f53316526%2frevoke-permission-from-the-permission-list-issue%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
No, if you go to setting and revoke permissions of an app, the app just lost focus and also in background, you could see it in recent apps list.
When you finish revoking and return to the app, it comes to foreground and corresponding life cycle callback would be triggered. And if the app need these permissions to run, but which be revoked by user, the app should run abnormally!
That's incorrect. There may be a screenshot of the app in the recents list, but it's no longer running. You can see this e.g. by looking at the running activities withadb shell dumpsys activity activities
. Regarding "if the app need these permissions to run, but which be revoked by user, the app should run abnormally" - an app should never assume that it still has a permission just because the permission was granted at some point in the past. It should always request the necessary permission right before performing the action that requires the permission.
– Michael
Nov 15 '18 at 12:59
Yes, after android 6.0, we should request permissions explicitly.
– navylover
Nov 15 '18 at 13:36
add a comment |
No, if you go to setting and revoke permissions of an app, the app just lost focus and also in background, you could see it in recent apps list.
When you finish revoking and return to the app, it comes to foreground and corresponding life cycle callback would be triggered. And if the app need these permissions to run, but which be revoked by user, the app should run abnormally!
That's incorrect. There may be a screenshot of the app in the recents list, but it's no longer running. You can see this e.g. by looking at the running activities withadb shell dumpsys activity activities
. Regarding "if the app need these permissions to run, but which be revoked by user, the app should run abnormally" - an app should never assume that it still has a permission just because the permission was granted at some point in the past. It should always request the necessary permission right before performing the action that requires the permission.
– Michael
Nov 15 '18 at 12:59
Yes, after android 6.0, we should request permissions explicitly.
– navylover
Nov 15 '18 at 13:36
add a comment |
No, if you go to setting and revoke permissions of an app, the app just lost focus and also in background, you could see it in recent apps list.
When you finish revoking and return to the app, it comes to foreground and corresponding life cycle callback would be triggered. And if the app need these permissions to run, but which be revoked by user, the app should run abnormally!
No, if you go to setting and revoke permissions of an app, the app just lost focus and also in background, you could see it in recent apps list.
When you finish revoking and return to the app, it comes to foreground and corresponding life cycle callback would be triggered. And if the app need these permissions to run, but which be revoked by user, the app should run abnormally!
answered Nov 15 '18 at 10:05
navylovernavylover
3,51531119
3,51531119
That's incorrect. There may be a screenshot of the app in the recents list, but it's no longer running. You can see this e.g. by looking at the running activities withadb shell dumpsys activity activities
. Regarding "if the app need these permissions to run, but which be revoked by user, the app should run abnormally" - an app should never assume that it still has a permission just because the permission was granted at some point in the past. It should always request the necessary permission right before performing the action that requires the permission.
– Michael
Nov 15 '18 at 12:59
Yes, after android 6.0, we should request permissions explicitly.
– navylover
Nov 15 '18 at 13:36
add a comment |
That's incorrect. There may be a screenshot of the app in the recents list, but it's no longer running. You can see this e.g. by looking at the running activities withadb shell dumpsys activity activities
. Regarding "if the app need these permissions to run, but which be revoked by user, the app should run abnormally" - an app should never assume that it still has a permission just because the permission was granted at some point in the past. It should always request the necessary permission right before performing the action that requires the permission.
– Michael
Nov 15 '18 at 12:59
Yes, after android 6.0, we should request permissions explicitly.
– navylover
Nov 15 '18 at 13:36
That's incorrect. There may be a screenshot of the app in the recents list, but it's no longer running. You can see this e.g. by looking at the running activities with
adb shell dumpsys activity activities
. Regarding "if the app need these permissions to run, but which be revoked by user, the app should run abnormally" - an app should never assume that it still has a permission just because the permission was granted at some point in the past. It should always request the necessary permission right before performing the action that requires the permission.– Michael
Nov 15 '18 at 12:59
That's incorrect. There may be a screenshot of the app in the recents list, but it's no longer running. You can see this e.g. by looking at the running activities with
adb shell dumpsys activity activities
. Regarding "if the app need these permissions to run, but which be revoked by user, the app should run abnormally" - an app should never assume that it still has a permission just because the permission was granted at some point in the past. It should always request the necessary permission right before performing the action that requires the permission.– Michael
Nov 15 '18 at 12:59
Yes, after android 6.0, we should request permissions explicitly.
– navylover
Nov 15 '18 at 13:36
Yes, after android 6.0, we should request permissions explicitly.
– navylover
Nov 15 '18 at 13:36
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%2f53316526%2frevoke-permission-from-the-permission-list-issue%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
Can anyone confirm this? - yes, you can. Revoke the permission and see what happens. It's not hard.
– Tim Castelijns
Nov 15 '18 at 9:54
It is possible to make the app restart after revoke permission by itself?
– Shalev Cohen
Nov 15 '18 at 9:56