Nativescript Webviewinterface Callback not working when you navigate back
I am asking this question here because the github repo of the nativescript webviewinterface seems to be pretty inactive.
Basically I want to execute a JS function from Nativescript and get a result. This works fine with the webviewinterface plugin for the most part. When you navigate back however it does not work anymore. The JS function still gets executed but the nativescript callback will not execute anymore.
This seems like a fairly common use case to me. Here is an example repo: https://github.com/ll9/ns-webview-callback-bug (When you first hit 'call js' you will get a console.log but when you navigate back it woll not work anymore)
Does anybody have a solution to this problem?
nativescript
asked Nov 17 '18 at 20:37
ll9Xll9X
1014
add a comment |
I am asking this question here because the github repo of the nativescript webviewinterface seems to be pretty inactive.
Basically I want to execute a JS function from Nativescript and get a result. This works fine with the webviewinterface plugin for the most part. When you navigate back however it does not work anymore. The JS function still gets executed but the nativescript callback will not execute anymore.
This seems like a fairly common use case to me. Here is an example repo: https://github.com/ll9/ns-webview-callback-bug (When you first hit 'call js' you will get a console.log but when you navigate back it woll not work anymore)
Does anybody have a solution to this problem?
nativescript
asked Nov 17 '18 at 20:37
ll9Xll9X
1014
Is it specific to a platform? At least it worked for me with iOS - still logs'js got called'after navigating back from second page.
– Manoj
Nov 17 '18 at 22:18
Hmm then it seems to be platform specific. I am using android and when I navigate back I do not getjs got calledanymore.
– ll9X
Nov 18 '18 at 10:30
Just to be clear: When you navigate from the last page back to the webviewjs got calleddoes not execute the callback anymore.
– ll9X
Nov 18 '18 at 10:54
add a comment |
I am asking this question here because the github repo of the nativescript webviewinterface seems to be pretty inactive.
Basically I want to execute a JS function from Nativescript and get a result. This works fine with the webviewinterface plugin for the most part. When you navigate back however it does not work anymore. The JS function still gets executed but the nativescript callback will not execute anymore.
This seems like a fairly common use case to me. Here is an example repo: https://github.com/ll9/ns-webview-callback-bug (When you first hit 'call js' you will get a console.log but when you navigate back it woll not work anymore)
Does anybody have a solution to this problem?
nativescript
asked Nov 17 '18 at 20:37
ll9Xll9X
1014
I am asking this question here because the github repo of the nativescript webviewinterface seems to be pretty inactive.
Basically I want to execute a JS function from Nativescript and get a result. This works fine with the webviewinterface plugin for the most part. When you navigate back however it does not work anymore. The JS function still gets executed but the nativescript callback will not execute anymore.
This seems like a fairly common use case to me. Here is an example repo: https://github.com/ll9/ns-webview-callback-bug (When you first hit 'call js' you will get a console.log but when you navigate back it woll not work anymore)
Does anybody have a solution to this problem?
nativescript
nativescript
asked Nov 17 '18 at 20:37
ll9Xll9X
1014
asked Nov 17 '18 at 20:37
ll9Xll9X
1014
asked Nov 17 '18 at 20:37
ll9Xll9X
1014
asked Nov 17 '18 at 20:37
ll9Xll9X
1014
asked Nov 17 '18 at 20:37
ll9Xll9X
1014
1014
Is it specific to a platform? At least it worked for me with iOS - still logs'js got called'after navigating back from second page.
– Manoj
Nov 17 '18 at 22:18
Hmm then it seems to be platform specific. I am using android and when I navigate back I do not getjs got calledanymore.
– ll9X
Nov 18 '18 at 10:30
Just to be clear: When you navigate from the last page back to the webviewjs got calleddoes not execute the callback anymore.
– ll9X
Nov 18 '18 at 10:54
add a comment |
Is it specific to a platform? At least it worked for me with iOS - still logs'js got called'after navigating back from second page.
– Manoj
Nov 17 '18 at 22:18
Hmm then it seems to be platform specific. I am using android and when I navigate back I do not getjs got calledanymore.
– ll9X
Nov 18 '18 at 10:30
Just to be clear: When you navigate from the last page back to the webviewjs got calleddoes not execute the callback anymore.
– ll9X
Nov 18 '18 at 10:54
Is it specific to a platform? At least it worked for me with iOS - still logs
'js got called' after navigating back from second page.– Manoj
Nov 17 '18 at 22:18
Is it specific to a platform? At least it worked for me with iOS - still logs
'js got called' after navigating back from second page.– Manoj
Nov 17 '18 at 22:18
Hmm then it seems to be platform specific. I am using android and when I navigate back I do not get
js got calledanymore.– ll9X
Nov 18 '18 at 10:30
Hmm then it seems to be platform specific. I am using android and when I navigate back I do not get
js got calledanymore.– ll9X
Nov 18 '18 at 10:30
Just to be clear: When you navigate from the last page back to the webview
js got called does not execute the callback anymore.– ll9X
Nov 18 '18 at 10:54
Just to be clear: When you navigate from the last page back to the webview
js got called does not execute the callback anymore.– ll9X
Nov 18 '18 at 10:54
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%2f53355344%2fnativescript-webviewinterface-callback-not-working-when-you-navigate-back%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%2f53355344%2fnativescript-webviewinterface-callback-not-working-when-you-navigate-back%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
Is it specific to a platform? At least it worked for me with iOS - still logs
'js got called'after navigating back from second page.– Manoj
Nov 17 '18 at 22:18
Hmm then it seems to be platform specific. I am using android and when I navigate back I do not get
js got calledanymore.– ll9X
Nov 18 '18 at 10:30
Just to be clear: When you navigate from the last page back to the webview
js got calleddoes not execute the callback anymore.– ll9X
Nov 18 '18 at 10:54