[Android] Custom intent not work in inappbrowser [net::ERR_UNKNOWN_URL_SCHEME]

[mosabab]

Bug Report

Problem

What is expected to happen?

Should deal with any name of custom scheme intent.

What does actually happen?

If you try to open external link for example via inappbrowser plugin, it open it without any problem, but if you click on any link in that website that have intent; with custom scheme name; then the inappbrowser plugin generate an error message from cordova webview:
net::ERR_UNKNOWN_URL_SCHEME

Information

Command or Code

Environment, Platform, Device

Version information

Cordova cli 10.0.0
cordova-android 9.1.0-dev (master version)
cordova-plugin-inappbrowser 5.0.0

Checklist

• I searched for existing GitHub issues
• I updated all Cordova tooling to most recent version
• I included all the necessary information above

[mosabab]

@erisu any idea regarding this issue!
Thanks

[erisu]

I havent looked at this yet but while reviewing and sorting PRs, I had noticed a PR with similar context.

• feat: handle intent:// scheme links with browser_fallback_url param cordova-android#1167

I only glanced over the code but didn't do a complete review yet.

[mosabab]

I havent looked at this yet but while reviewing and sorting PRs, I had noticed a PR with similar context.

• feat: handle intent:// scheme links with browser_fallback_url param cordova-android#1167

I only glanced over the code but didn't do a complete review yet.

Thanks for the explain.
If that issue got fixed will be good for next cordova-android release
Thanks

[mosabab]

I havent looked at this yet but while reviewing and sorting PRs, I had noticed a PR with similar context.

• feat: handle intent:// scheme links with browser_fallback_url param cordova-android#1167

I only glanced over the code but didn't do a complete review yet.

I think the Mentioned PR need to add some code to be in the correct way, because the custom scheme names not work with cordova web view, and the webview generate error message like this:
[net::ERR_UNKNOWN_URL_SCHEME].

@breautek Do you have any idea for this issue ?

Thanks all

[breautek]

My best guess is the fact that in-app-browser implements its own webview (as it's intended to have an isolated webview) https://github.com/apache/cordova-plugin-inappbrowser/blob/master/src/android/InAppBrowser.java#L916

apache/cordova-android#1167 is for the cordova webview so it won't have any effect on the in app webview.

Issues with the in-app browser webview should be reported for the in-app-browser plugin. Since I think it is desirable to have the same behaviour in this case, I'll move this ticket over to the proper repository.

[mosabab]

My best guess is the fact that in-app-browser implements its own webview (as it's intended to have an isolated webview) https://github.com/apache/cordova-plugin-inappbrowser/blob/master/src/android/InAppBrowser.java#L916

apache/cordova-android#1167 is for the cordova webview so it won't have any effect on the in app webview.

Issues with the in-app browser webview should be reported for the in-app-browser plugin. Since I think it is desirable to have the same behaviour in this case, I'll move this ticket over to the proper repository.

Thanks for explain

[mosabab]

@breautek
Hi, i found that if someone familiar with java code can fix this issue as fixed on android platform webview.
But unfortunatly i dont have any experinces in java codes.

Thanks