I updated my iPad to iOS 17.0.3 thinking maybe Apple was on top of this and that this would fix it. No such luck. All I get is a different error. I'm still hosed. BUG IN CLIENT OF libsqlite3.dylib: database integrity compromised by API violation: vnode unlinked while in use: /private/var/mobile/Containers/Data/Application/F69182D8-2930-4882-A8F6-D76179F1E87B.sb-857f9996-cxGWIo/Documents/MY_DB_File.sqlite invalidated open fd: 3 (0x11)

Cannot find 'BOOL' in scope Cannot find 'shouldAddStorePayment' in scope

Thanks for the rely. Where should I add this code?

silverthorne@protonmail.com

After more testing I've found that this does not run in AppDelegate. It's actually in a func inside AppDelegate that fires when the device is rotated. If you are still willing to help me out, Claude , I can post the complete code. Probably should have done that in the beginning. My bad. let firstScene = window?.windowScene if let w = firstScene as? UIWindowScene { let screenSize = w.screen.bounds print("screenSize", screenSize) }

Thank you, Claude. Your first method doesn't make the constraint value a % of the screen width, or does it? I've been using the second method already. I was thinking autolayout word be a better way to go. Most of my UI is set up to make the constraint values a % of the screen height/width. I've been setting the control to centered and adjusting the leading constraint using the screen width/height. Makes for cleaner layout. I guess I'll have to rethink the way I was planning to use autolayout.

Thanks again, Claude.

Thanks for the reply, @Claude31 I tried changing to did end on exit. It didn't fix the problem on iOS 15.6.1 and it caused things to not work correctly on iOS 5.5 too.

Thank you very much for the reply. I’m not sure if this is considered forward or backwards compatibility. Basically the problem occurs when I add a Xcode 13 button to a Xcode 12.5 project and leave the Deployment Target at 14.x. Also, and I know you’re very busy so please excuse my ignorance but would you please provide some code to help me better understand your answer? I’m not sure what you mean by “As part of the updateConfiguration pass on UIButton”.

In the test Xcode 12.5 project that was opened in Xcode 13, if I set the iOS Deployment Target to 15, it works fine. But that means that apps cannot support earlier versions of iOS. That also means that using @available(iOS 15.0, *) becomes meaningless.  The extensions in the 12.5 project do not exist in the test project. No warnings when the project is opened in Xcode 13.