[Bug]: BridgeFragment doesn't call WebView.destroy in Fragment.onDestroy()

[hbordersTwitch]

Capacitor Version

[warn] The bundledWebRuntime configuration option has been deprecated. Can be safely deleted. 💊 Capacitor Doctor 💊

Latest Dependencies:

@capacitor/cli: 6.1.1 @capacitor/core: 6.1.1 @capacitor/android: 6.1.1 @capacitor/ios: 6.1.1

Installed Dependencies:

@capacitor/cli: 6.1.1 @capacitor/ios: 6.1.1 @capacitor/android: 6.1.1 @capacitor/core: 6.1.1

[success] iOS looking great! 👌 [success] Android looking great! 👌

Other API Details

$ npm --version
10.7.0
$ node --version
v22.2.0
$ pod --version
1.15.2

Platforms Affected

• [ ] iOS
• [X] Android
• [ ] Web

Current Behavior

BridgeFragment.onDestroy() calls Bridge.onDestroy(), but Bridge.onDestroy() does not call WebView.destroy().

This matters because if we don't call WebView.onDestroy(), the WebView leaks its WebMessageListener instances. Capacitor's WebMessageListener holds a references to the CapacitorWebView, which holds a reference to the Bridge, which holds a reference to the BridgeFragment.

Expected Behavior

After BridgeFragment.onDestroy(), Capacitor cleans up all resources

Project Reproduction

Please let me know if you require a repro for this.

Additional Information

One can work around this by extending BridgeFragment.onDestroy() and calling bridge.getWebView().destroy() manually.

Thank you for this project!