Some problem with javascriptHanlder

[yhdjy025]

My window.flutter_inappbrowser object have a method named _callHandler but not callHandler
and I call this method, _callHandler in my JS code, but the InAppWebViewController can not recive the call

My js code:

  console.log('----------------------_callHandler--------------')
            console.log(window.flutter_inappbrowser._callHandler)
            console.log('----------------------callHandler--------------')
            console.log(window.flutter_inappbrowser.callHandler)
            //call app
            try {
                window.flutter_inappbrowser._callHandler('message', 'hello');
            } catch (e) {
                console.log(e)
            }

My dart code

return InAppWebView(
      initialUrl: Constant.SERVER_ADDRESS +
          'extendmng/zz/userIndex?apptype=2&userid=' +
          userInfo.userid +
          '&token=' +
          userInfo.token +
          '&os=' +
          (defaultTargetPlatform == TargetPlatform.android ? 'android' : 'ios'),
      initialHeaders: {},
      initialOptions: {'safeBrowsingEnabled': false},
      onWebViewCreated: (InAppWebViewController controller) {},
      onLoadStart: (InAppWebViewController controller, String url) {
        controller.addJavaScriptHandler('message', (params) {
          print(params.toString());
        });
      },
      onProgressChanged: (InAppWebViewController controller, int progress) {
        print('----------------' + progress.toString());
      },
      onConsoleMessage:
          (InAppWebViewController controller, ConsoleMessage consoleMessage) {
        print(consoleMessage.message);
      },
    );

see th picture

[pichillilorenzo]

Yeah I know! I fixed this problem in the last commit 👍 .. I need to update the documentation because there is a little change on how it works! Later I'm going to publish the new version

[pichillilorenzo]

Feature added now on the new version 1.1.0.
Inside an html file, you may want to use this:

<script>
        // you need to wait and listen the JavaScript event flutterInAppBrowserPlatformReady
        window.addEventListener("flutterInAppBrowserPlatformReady", function(event) {
            console.log("ready");
            // then you can call the window.flutter_inappbrowser.callHandler() method.
            // callHandler() returns a Promise that you can use to get data from Dart side.
            window.flutter_inappbrowser.callHandler('handlerFoo').then(function(result) {
                console.log(result, typeof result);
                console.log(JSON.stringify(result), result.bar);
            });

            window.flutter_inappbrowser.callHandler('handlerFooWithArgs', 1, true, ['bar', 5], {foo: 'baz'}).then(function(result) {
                console.log(result, typeof result);
                console.log(JSON.stringify(result));
            });
        });
</script>

Instead, on the onLoadStop Dart event, you can use callHandler directly:

// Inject JavaScript that will receive data back from Flutter
webView.injectScriptCode("""
  window.flutter_inappbrowser.callHandler('test', 'Text from Javascript').then(function(result) {
    console.log(result);
  });
""");

[yhdjy025]

I have tested in some diff version SDK android emulator,I find some devices do not have callHandler function in window.flutter_inappbrowser object,.so I guess there has compatible problem on it.

[pichillilorenzo]

Which version?? Thanks

[yhdjy025]

I use the Genymotion to create a Nexus 5 - API23 of Android emulator.
look at the picture

And it continuous print W/art ' ( 1866): Attempt to remove non-JNI local reference, dumping thread='

[yhdjy025]

I find the _callHandler function is exist,
Means the object add by addJavascriptInterface function is success, and add by evaluateJavascript is failed

[pichillilorenzo]

Ok! I will try that!

[yhdjy025]

I've found the reason. look at the screenshot

because the ...args is support in ES6, some android simulator's browser core do not support it.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue.