I recently switched to using SafariViewController for our oauth2 flow. We were previously using InAppBrowser. With InAppBrowser is debuggable was set to true in the Android manifest then self-signed certificates were allowed an the InAppBrowser never showed the prompt to accept the certificate. This doesn't appear to be the case with SafariViewController, and it affects my Appium functional tests. Has anyone come across this or know a solution for this? Of course once I accept the certificates I am fine, but this means I have to do this for all my test devices and hope the browser cache doesn't get clear. This is only for our test environment where we have self-signed certificates. Our production version doesn't have this issue.
I recently switched to using SafariViewController for our oauth2 flow. We were previously using InAppBrowser. With InAppBrowser is debuggable was set to true in the Android manifest then self-signed certificates were allowed an the InAppBrowser never showed the prompt to accept the certificate. This doesn't appear to be the case with SafariViewController, and it affects my Appium functional tests. Has anyone come across this or know a solution for this? Of course once I accept the certificates I am fine, but this means I have to do this for all my test devices and hope the browser cache doesn't get clear. This is only for our test environment where we have self-signed certificates. Our production version doesn't have this issue.