I'd like to know if adopting future SwiftUI APIs would not require that I keep supporting only the latest and greatest versions of each OS (iOS / macOS / watchOS). In theory, would I still be able to at least support iOS 13 going forward, even if I were to use new API introduced in iOS 14 for SwiftUI? In theory the runtime bundled with our apps should be backward compatible with iOS 13?

I've got a macOS app with a "Helper" (LoginItem) app that I'd like to attach the debugger to in order to debug the communication between the two.I realize hardening a target makes it impossible to attach the Xcode debugger to it, however I've created a separate entitlements file for Debug mode, turned "Enable Hardening" OFF for both Debug targets and have also added a "com.apple.security.get-task-allow" set to "YES" in the entitlement files for both debug targets. Still, I see this:macOSTaskPolicy: (com.apple.debugserver) may not get the taskport of (com.b) (pid: 4144): (com.b) is hardened, (com.b) doesn't have get-task-allow, (com.apple.debugserver) is a declared debuggerI'm unable to debug the helper and it's frustrating. How can I disable SIIP or whatever it takes to get this to work?

Suddenly, automatic signing has stopped working across all our apps (even on different developer IDs), we see this:Automatic Signing FialedXcode failed to provision this target. Please file a bug report at <https://feedbackassistant.apple.com> and include the Update Signing report from the Report navigator.Signing certificate "Apple Development: XXXXX (XXXXX)", serial number "XXXXX", is not valid for code signing. It may have been revoked or expired.Anyone else experiencing the same? I've tried doing everything from deleting the derived folder, to trying to reset and create new certificates to trying different versions of Xcode. Everything fails and I get a prolonged "Waiting to repair" message first and then this.

I'm trying to use the Accessibility API and have this code: NSDictionary *options = @{(__bridge id) kAXTrustedCheckOptionPrompt : @YES}; BOOL accessibilityEnabled = AXIsProcessTrustedWithOptions((__bridge CFDictionaryRef) options);This always returns no, however it does not prompt the user for permission nor does it display the app's name in System Preferences > Security & Privacy. What do I need to test this? I could try and add the debug version manually into System Preferences but how do I know that this will work properly when released to the public? Is there any way to test this out? I am not seeing any prompt at all.