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
After updating CAS version from 3.9.0 to 3.9.1 (we are using Optimal), all alerts started to force orientation change to portrait.
dJVmdTTa.mp4
And if the orientation is locked to landscape (what we have in production currently), the app crashes.
*** Terminating app due to uncaught exception 'UIApplicationInvalidInterfaceOrientation', reason: 'Supported orientations has no common orientation with the application, and [SwiftUI.PlatformAlertController shouldAutorotate] is returning YES'
It seems to get fixed after subclassing UIAlertController and adding a call to setNeedsUpdateOfSupportedInterfaceOrientations
After some investigation I've found, that the issue is probably in CASExchange adapter, because adding all Optimal adapters without it makes the bug disappear and vice-versa (adding only CASExchange brings the bug).
The same bug appears in CAS version 3.9.3
The text was updated successfully, but these errors were encountered:
Hello @levochkaa,
Thank you for reporting this issue. We are currently investigating to determine the root cause. We appreciate your patience and will update you as soon as we have more information.
After updating CAS version from 3.9.0 to 3.9.1 (we are using Optimal), all alerts started to force orientation change to portrait.
dJVmdTTa.mp4
And if the orientation is locked to landscape (what we have in production currently), the app crashes.
It seems to get fixed after subclassing
UIAlertController
and adding a call tosetNeedsUpdateOfSupportedInterfaceOrientations
...but we have SwiftUI alerts..
After some investigation I've found, that the issue is probably in CASExchange adapter, because adding all Optimal adapters without it makes the bug disappear and vice-versa (adding only CASExchange brings the bug).
The same bug appears in CAS version 3.9.3
The text was updated successfully, but these errors were encountered: