I do this, too. Is your app written in Swift or ObjC? I use something like this: @Environment(\.scenePhase) private var scenePhase ... .onChange(of: scenePhase) { if(scenePhase == .active) { // Remove blocking view } else if(scenePhase == .inactive) { // Add blocking view } } Also, make sure you're using a new LAContext() every time you need to use it. I was using a global context and it only worked sporadically.

I can't speak to timing, but what will happen has to happen in an iOS update. There will be a future version of iOS where an application that does not support the scene-based lifecycle will not launch. So, let's look at the options: You have an existing app on the App Store. You released it ages ago. It uses the app lifecycle. You have not updated it to use the scene-based lifecycle. This app will launch on older versions of iOS, but it will not launch on the new version of iOS. (This will trim a lot of old apps from the App Store.) You have an existing app on the App Store. You released it ages ago. It uses the app lifecycle. You update it to use the scene-based lifecycle. This app launches on the old versions of iOS, and the new version of iOS. You're developing an app in Xcode that supports an older version of iOS that allows the app lifecycle method, and your app uses that app lifecycle method. You can build this app and run it on that version of iOS without issue. It launches fine. If you attempt to run it on the latest version of iOS, it will not launch. You're developing an app in Xcode that supports an older version of iOS that allows the old lifecycle method, but your app uses the new scene-based lifecycle method. You can build this app and run it on the old version of iOS without issue. It launches fine. If you run it on the latest version of iOS, it launches fine. Now, all new builds submitted to the App Store are supposed to support the latest version of iOS, so when Apple release this new version of iOS that requires the scene-based lifecycle method, and you attempt to upload an app that does not use the scene-based lifecycle method then your app will likely be rejected by the upload or validation process. As an aside, I recently updated four of my apps to use the scene-based lifecycle, and it was painless. If you need help in migrating, just start a new app in Xcode and it will have the scene-based lifecycle in it. You can see how it's structured and just copy the bits into your existing app. Sure, you might need to rework some things, but it's nowhere near as big a deal as you might think.

Well, umm, thanks for the feedback... You do realise (don't you?) that these forums - where you were able to sign up as a not-employed-by-Apple person - are not where Apple's employees hang out and discuss what they're doing in the platform code? If you have a suggestion, you can raise it at: https://feedbackassistant.apple.com/

Hard to tell why your app crashes if you don't give us any indication of what's crashing. How about a crash report, or showing us the lines of code where the crash occurs? Also, give us the versions of iOS that are crashing, and the version of Xcode you built your app with.

No, you cannot downgrade from 26 beta to 11.5. It's not possible. It's exceptionally important to read the details of the upgrade and downgrade paths before you do anything, as you have now discovered. Sorry.

You already posted about this here: https://developer.apple.com/forums/thread/788049 Apple responded to you and you marked it as the accepted answer. Claude31 also provided you with a standard info.plist file that you could use to recreate your own. Did you even attempt to follow his suggestion? Where did you get your screenshot above from?

Have you raised a Feedback report? If not, please do so at https://feedbackassistant.apple.com/ then post the FB number here.

Guys, these are the Developer Forums, where third-party developers ask each other for hints and tips on how to code their apps for Apple's platforms. It's great that you've found bugs in the new betas of the operating systems and are talking about them, but posting about them in these forums isn't going to progress them unless you also raise them as bugs in the usual place, which is not these Developer Forums. Apple's developers aren't sitting around reading these forums, waiting for things to fix. Please raise each bug separately at: https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

If it's fine on the device, then you should raise it as a bug in the Simulator at: https://feedbackassistant.apple.com/

Please don't post screenshots of errors. They cannot be searched for, so if this post gets a solution someone with the same error will not be able to find it. Have you debugged your code?

You cannot submit apps to the App Store where any part of your toolchain is a beta version, which means you can't use Xcode 16.4 on macOS 26 beta. This was recently answered by Ed Ford from Apple here: https://developer.apple.com/forums/thread/787654

You should raise this as a suggestion here: https://feedbackassistant.apple.com/ If multiple people raise similar feedback, Apple will listen and might reintroduce it. However, the changes made in iPadOS 26 are quite extensive, and it may not be possible to bring them back. You might want to make some suggestions as to how to activate the features etc.

Isn't this how it's supposed to work now? The keynote explained this at 0:10:42: and the result at 0:10:47: So, your buttons get smushed over to the left. I think you just need to work on your tab bar.

The Revolut app was written and tested for iOS 18, not iOS 26. If it doesn't work it's up to Revolut to fix the issues and release it when iOS 26 is released. This is precisely why you should never install the beta versions on your primary device. If you can no longer access your banking app, well...

The documentation is likely out of date, and you may want to raise a feedback report to Apple to have it updated: https://feedbackassistant.apple.com/ macOS Sequoia introduced the Passwords app, which meant you didn't really need to use Keychain Access anymore. However, as you've noticed, you do need it for some things. It's now in System > Library > CoreServices > Applications, but the easiest way to get to it is with Spotlight.