You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been using COSTouchVisualizerWindow in our apps for years, in a non active state at launch and can be enable by a switch inside the app. It didn't have any problems so far. However, since some iOS 16 version, even if the fingertips display is not enabled by the delegate (touchVisualizerWindowShouldShowFingertip returning false), there is a strange behavior:
our navigation controller and top view controller only allow landscape rotations (through supportedInterfaceOrientations); it worked well before
since maybe iOS 16.0 we don't know exactly, if the app is launched and no tap is performed at all, the rotation works as expected: we turn the iPad and the window only rotates when it goes from landscape left to landscape right and the other way round
after any tap on the screen (ie. anywhere, without hitting any button or active element), the rotation gets broken: when rotating the iPad to portrait, the window has a rotation animation (we see the black corners rotating) while the controller stays landscape, and many other things get broken like the keyboard is showing in portrait, modals are portrait, ...
if we replace COSTouchVisualizerWindow by UIWindow, the problem doesn't appear
Very strange behavior, would anyone have any ideas?
We are using tag 1.0.6.
The text was updated successfully, but these errors were encountered:
Hi,
We have been using COSTouchVisualizerWindow in our apps for years, in a non active state at launch and can be enable by a switch inside the app. It didn't have any problems so far. However, since some iOS 16 version, even if the fingertips display is not enabled by the delegate (
touchVisualizerWindowShouldShowFingertip
returning false), there is a strange behavior:supportedInterfaceOrientations
); it worked well beforeVery strange behavior, would anyone have any ideas?
We are using tag 1.0.6.
The text was updated successfully, but these errors were encountered: