You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fatal Exception: java.lang.RuntimeException: Unknown feature WEB_MESSAGE_LISTENER
at androidx.webkit.internal.WebViewFeatureInternal.isSupported(WebViewFeatureInternal.java:628)
at androidx.webkit.internal.WebViewFeatureInternal.isSupported(WebViewFeatureInternal.java:597)
at androidx.webkit.WebViewFeature.isFeatureSupported(WebViewFeature.java:591)
at com.getcapacitor.MessageHandler.<init>(MessageHandler.java:26)
at com.getcapacitor.Bridge.<init>(Bridge.java:220)
at com.getcapacitor.Bridge$Builder.create(Bridge.java:1560)
at com.getcapacitor.BridgeFragment.load(BridgeFragment.java:86)
when running on Chromebooks with Android 11. Specifically:
96% - Google Cros:
83% -AMD Stoney Ridge Chromebook
9% - Intel Jasper Lake Chromebook
4% - Intel Gemini Lake Chromebook
4% - Hewlett-Packard
4% - 1650
Expected Behavior
Capacitor should not crash when a
Project Reproduction
I can't reproduce this because I don't have a Chromebook running Android 11
Capacitor Version
$ npx cap doctor
[warn] The bundledWebRuntime configuration option has been deprecated. Can be safely deleted.
💊 Capacitor Doctor 💊
Latest Dependencies:
@capacitor/cli: unknown
@capacitor/core: unknown
@capacitor/android: unknown
@capacitor/ios: unknown
Installed Dependencies:
@capacitor/cli: 6.1.1
@capacitor/core: 6.1.1
@capacitor/android: 6.1.1
@capacitor/ios: 6.1.1
[success] iOS looking great! 👌
[success] Android looking great! 👌
Other API Details
Platforms Affected
Current Behavior
I have the following crash:
when running on Chromebooks with Android 11. Specifically:
Expected Behavior
Capacitor should not crash when a
Project Reproduction
I can't reproduce this because I don't have a Chromebook running Android 11
Additional Information
This code still exists in 7.0.1's
MessageHandler.java
, so I suspect this is still a7.0.1
bug.I suggest the following:
The text was updated successfully, but these errors were encountered: