We used to be able to enter usernames / passwords in SFSafariViewController by running the query app.webViews but we're no longer able to do so.
Does anyone know how to do this with Xcode 11.3 ?
thanks,
David
We used to be able to enter usernames / passwords in SFSafariViewController by running the query app.webViews but we're no longer able to do so.
Does anyone know how to do this with Xcode 11.3 ?
thanks,
David
Have you found any workaround for this issue yet? Having this issue too: app.webViews are there but are "empty", we cannot see what is in them or interact with them.
Same issue here. I am using native view context here and it times out upon finding the textfield. This issue is very specific to IOS 13.3.
I too encountered this and logged it as FB7513956. Please make sure you log similar feedbacks so that it can get addressed.
This is not resolved with Xcode 11.3.1 and iOS 13.3.1 beta 2
Facing same problem on 11.3.1 and iOS 13.3.1 beta 2
I've raised a feedback message for this: FB7537885
Hello, wondering if you have received any reply in that feedback ticket. I have opened a similar one (7529542) but no reply yet.
This issue is blocking us for running our automated tests 😟
Thanks!
I received this update this morning: "Potential fix identified - For a future OS update". So, look out for a new beta release I guess?
Thanks for your reply! looking forward to that new update then 🙂 Hopefully it happens soon...
This is not resolved with Xcode 11.3.1 (11C505) and iOS 13.3.1 beta 3 (17D5050a)
No fix on 13.3.1 beta 3 :/ so suppose we will have to wait until beta 4 will be released :/
I have the same status: "Potential fix identified - For a future OS update"
In case anyone else is interested, I got around this by using the 13.2.2 simulator in my UI tests.
You can have multiple schemes and tick which tests to run, so if you have a subset of tests that need 13.2.2, you can tick the tests to run in that scheme only (and untick them in the other scheme) - then if you've got a CI / buld server with a script calling xcodebuild you can specify the different scheme and different simulator version, something lke:
-scheme "ui-tests-only-for-13.2.2" -destination "platform=iOS Simulator,name=iPhone 11,OS=13.2.2"
We're just using 13.2.2 for all our tests - but that above is (possibly) a workaround if you need to split out tests on a build server for iOS 13.3 specifically (depends if you're not bothered about testing other features of SFSafariViewController on 13.3 though!)
We plan on doing this until we need something specific about iOS 13.3 for SFSafariViewController.
Fingers crossed Apple will sort it out for iOS 14 😉
I think part of the problem is addressed with Xcode 11.4 beta (11N111s) and iOS 13.4 beta 1 (17E5223h). The UI automation tests are able to successfully interact with SFSafariViewController and ASWebAuthenticationSession, however, the tap event causes the text action menu (cut, copy, paste, select all) to come up and the test idles itself while that is visible. Dismissing this causes some text input to be incomplete, leading to test failures. Is anyone else experiencing the same behavior?
can confirm that it is working on my side as well, and looks alright.