WillPopScope should I use return Future.value(true) after Navigator.pop
Is using return Future.value(false);
after Navigator.pop(context)
is the right way.
If I use
Navigator.pop(context, false)
and after it
return Future.value(true);
The application will show black screen after pressing the back button, and no errors in the Logcat.
But if I use the same code without the Navigator.pop(context)
or without the return Future.value(true);
everything will be fine, using return Future.value(false);
also works fine.
*Following a tutorial on Udemy that show return Future.value(true)
is ok.

add a comment |
Is using return Future.value(false);
after Navigator.pop(context)
is the right way.
If I use
Navigator.pop(context, false)
and after it
return Future.value(true);
The application will show black screen after pressing the back button, and no errors in the Logcat.
But if I use the same code without the Navigator.pop(context)
or without the return Future.value(true);
everything will be fine, using return Future.value(false);
also works fine.
*Following a tutorial on Udemy that show return Future.value(true)
is ok.

add a comment |
Is using return Future.value(false);
after Navigator.pop(context)
is the right way.
If I use
Navigator.pop(context, false)
and after it
return Future.value(true);
The application will show black screen after pressing the back button, and no errors in the Logcat.
But if I use the same code without the Navigator.pop(context)
or without the return Future.value(true);
everything will be fine, using return Future.value(false);
also works fine.
*Following a tutorial on Udemy that show return Future.value(true)
is ok.

Is using return Future.value(false);
after Navigator.pop(context)
is the right way.
If I use
Navigator.pop(context, false)
and after it
return Future.value(true);
The application will show black screen after pressing the back button, and no errors in the Logcat.
But if I use the same code without the Navigator.pop(context)
or without the return Future.value(true);
everything will be fine, using return Future.value(false);
also works fine.
*Following a tutorial on Udemy that show return Future.value(true)
is ok.


edited Jan 1 at 17:21
Saed Nabil
1,27329
1,27329
asked Jan 1 at 13:04


guyguy
660214
660214
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I found the solution.
You should use return Future.value(false);
.
You navigated manually by using Navigator.pop(context)
, Future.value(true);
trigger another pop which can't be done because you already exist the page and this crashes the app.
OnWillPop expect a return so By using the return Future.value(false);
you tell the onWillPop that you handle the closing of the page here.
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%2f53995673%2fwillpopscope-should-i-use-return-future-valuetrue-after-navigator-pop%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
I found the solution.
You should use return Future.value(false);
.
You navigated manually by using Navigator.pop(context)
, Future.value(true);
trigger another pop which can't be done because you already exist the page and this crashes the app.
OnWillPop expect a return so By using the return Future.value(false);
you tell the onWillPop that you handle the closing of the page here.
add a comment |
I found the solution.
You should use return Future.value(false);
.
You navigated manually by using Navigator.pop(context)
, Future.value(true);
trigger another pop which can't be done because you already exist the page and this crashes the app.
OnWillPop expect a return so By using the return Future.value(false);
you tell the onWillPop that you handle the closing of the page here.
add a comment |
I found the solution.
You should use return Future.value(false);
.
You navigated manually by using Navigator.pop(context)
, Future.value(true);
trigger another pop which can't be done because you already exist the page and this crashes the app.
OnWillPop expect a return so By using the return Future.value(false);
you tell the onWillPop that you handle the closing of the page here.
I found the solution.
You should use return Future.value(false);
.
You navigated manually by using Navigator.pop(context)
, Future.value(true);
trigger another pop which can't be done because you already exist the page and this crashes the app.
OnWillPop expect a return so By using the return Future.value(false);
you tell the onWillPop that you handle the closing of the page here.
edited Jan 3 at 8:03
answered Jan 3 at 7:56


guyguy
660214
660214
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%2f53995673%2fwillpopscope-should-i-use-return-future-valuetrue-after-navigator-pop%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