Posts

Post not yet marked as solved
1 Replies
We have a similar problem.We noticed because after our app shows the user content in SFSafariViewController and the user navigates back to the original scene, all user touches are ignored by the original scene even though it is visible.I discovered that during this bad condition the view debugger shows 2 active windows: A UIWindowScene that contains the scene the user should be interacting with and _UIKeyboardWindowScene. Both of these top level objects in the view heirarchy are listed as "Foreground Active". When things are working only the main UIWindowScene is listed in the view debugger.My guess is that _UIKeyboardWindowScene is stealing all user input even tho it is not visible.How to trigger this condition:Top level scene A in our appUser taps buttonA presents sheet modal scene BUser taps buttonB presents SFSafariViewControllerSFSafariViewController page loadsUser taps compass iconSFSafariViewController opens page in Safari appPage loads in Safari appUser taps navigate back button in upper leftiOS navigated from Safari app back to our appUser taps DoneDismiss SFSafariViewControllerUser taps DoneDismiss sheet modal BUser attempts to tap on buttons in AScene A never receives user touches
Post not yet marked as solved
10 Replies
I have noticed the same defect. WCSession's `transferUserInfo` is broken between Watch simulator and Phone simulator in Xcode 11.3 (perhaps all of Xcode 11 versions so far). No mention of it in any of the Xcode 11 release notes. Whereas `sendMessage` works fine. The exact same code works on real device but silently fails on simulator. This code worked on simulator just fine in Xcode 10.This defect is shameful for the Simualtor team. They should have system tests that exercise `transferUserInfo` as well as `sendMessage`.