Banking Apps - and your banking data with it - typically get hardened against code injection and code changes. This is pretty dependent on the ABI and runtime format, which probably changed with iOS 16 (like with nearly every OS release). Bottom line: Don't install an OS beta on your production device.

The code is pretty nested in the inner area of the app something like  if (! _rootController) {         if([UIDevice currentDevice].userInterfaceIdiom == UIUserInterfaceIdiomPhone) { _rootController = [[IPhoneRootController alloc] init]; } else { _rootController = [[IPadRootConroller alloc] init]; } UIUserInterfaceIdiomPhone == 0, so either userInterfaceIdiom is 0 or UIDevice.currentDevice is nil.

Yes, AFAIK the code is executed in the main thread, in the meantime the main thread was blocked twice for short pseudo-sync network calls (I know this is a bad practice, the code comes from iOS 6...)

So we get a big usuability regression (at least for me) because the fear of (hopefully otherwise prevented) malware? Sorry, the vision of what Apple wants to allow me to do due to questionable security concerns on my hardware gets more and more out of sync with what I want and need to do. (See also the overboarding permission dialogs.).