To reply to my own reply:I just confirmed that I cannot repro my problem if I build against a 13.2 simulator. Building against 13.2, I am able to get at the descendants of my webview just fine.So other SDETs/QA Engineers out there, we may be tripping across a bug in 13.3 here, or possibly in Xcode 11.3.1. If you have the option, you may just have to test for now against 13.2.We'll need to keep an eye on further Xcode updates to see if this issue gets resolved.
annathepiper
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
I'm seeing this exact same problem. I'm an SDET asked to do research at my current position on whether I can write XCUITest automation against an internal hybrid app we have.When I fired up our app inside my Xcode, I got output in my debugger identical to the above. This sure looks like a possible iOS/iPadOS 13.3 bug. Or possibly an Xcode 11.3.1 bug?I'm about to confirm whether I can repro the problem with a 13.2 simulator.