Cap-go/capacitor-inappbrowser

Capacitor 6.0.0-rc.0 IOS build error: Value of type 'WKWebView' has no member 'isInspectable'

Closed this issue · 5 comments

Hi,
i just update my version to the latest avaliable npm version -> 1.3.3 and when i try to build the IOS i see the following error.

/node_modules/@capgo/inappbrowser/ios/Plugin/WKWebViewController.swift:220:21: error: value of type 'WKWebView' has no member 'isInspectable'

Thanks,

Hello we have the same issue. we have clients on production using android 14 which needs capacitor 6 to work.
After the update of capacitor 6-rc0 inappBrowser plugin(v 1.3.3) throws the above exception for ios devices only (android works) while building the project for production. If we keep using the version 1.2.20 with capacitor/ios (v 5.0.7) for ios is working but not in android and also we have to use --force on npm install for the other libraries which is not safe.

is there any option to release any new version fixing this? Is there any workaround for the above error in order to use capacitor 6 on both ios and android?

thank you

I can have a look but i'm not sure why do you update to capacitor 6?
you can allow it working with capacitor 5:
ionic-team/capacitor-plugins#1823 (comment)
and example of fix i had to do for android 14 without doing a whole switch to capacitor 6:
https://github.com/Cap-go/capacitor-updater/pull/284/files

I believe this is more an issue to report in Capacitor Repo as isInspectable is somethig require if we want to keep be able to inspect in the webview.
Can you open an issue there ?

i got the same issue in my CI/CD with capacitor 5 so i'm using the fix here:
https://stackoverflow.com/questions/76216183/how-to-debug-wkwebview-in-ios-16-4-1-using-xcode-14-2/76603043#76603043
this should resolve your issue as well in 1.3.15

i got the same issue in my CI/CD with capacitor 5 so i'm using the fix here: https://stackoverflow.com/questions/76216183/how-to-debug-wkwebview-in-ios-16-4-1-using-xcode-14-2/76603043#76603043 this should resolve your issue as well in 1.3.15

Thank you @riderx for your support. We will give it a try with the latest version 1.3.15.