Hi Julien, Ability to accept self-signed certificates for development builds sounds like a neat enhancement and I personally would give my thumbs up for this kind of feature. I would be hesitant to allow self-signed certificates for release builds. I'm wondering if this could be adapted to either an independent plugin or be incorporated into cordova-ios package. The cordova-plugin-wkwebview-engine package while not officially declared deprecated... will become obsolete soon given that it's only supported for cordova-ios <= 5.x. It's pending a formal vote and I think one last release for official deprecation. As of cordova-ios@6 WKWebView is built into the core platform and UIWebView is physically removed from the codebase.
So if this could be adapted to support cordova-ios@6, I think that would be better in the long term. Kind regards, Norman On Dec 18 2020, at 6:21 pm, Julien Lamure <julien.lam...@nexjhealth.com> wrote: > Hello everyone, > > I'm senior DevOps engineer and team lead at NexJ Health, greetings from > Toronto, Canada. > We're a provider of cloud-based population health management solutions and > our platform can also be accessed from a Cordova-based mobile app available > for Android and iOS. > I've been recently working on the migration to the WKWebView engine for iOS, > and I made a fork of cordova-plugin-wkwebview-engine that adds the ability to > accept self-signed certificates. > I'm not an iOS developer, it was the first time I was touching some > Objective-C code, but my patch is vastly inspired from what was done in > Oracle's cordova-plugin-wkwebview-file-xhr. > We needed this feature because our developers test our mobile app along with > a server instance hosted on there workstation, and this local instance uses > self-signed certificates. > > I was thinking of creating a pull request on the official > cordova-plugin-wkwebview-engine to share this feature with the community > since I could see a lot of people asking how to do it, please let me know if > it's something that you would like me to do so. > Our fork is currently in one of our private repositories. > > Cheers > Julien >
