https://clang.llvm.org/compatibility.html#inline-asm

What does the view hierarchy look like? Begin there.

Did you include the privacy statement string in the info.plist?

Serialize the operation allowing permitting the root to complete any reference updates.

Why not just use REST Apis?

I also work for a financial institution and good luck with that request. I can tell you now no such information is extractable unless you design for the user to provide it. Let alone why will a financial institution wan't access to text messages???

That should be macOS 12.1

This seems to be a problem with Monterey. I have noticed at times the click area sometimes is unresponsive, the cursor will move halfway across the screen or the UI doesn't respond to the first click. Wait and see what happens when 15.1 is release or you might have a swollen battery causing the track pad issue.

No. if the app offers no value other than spam ads.

import UIKit extension UIApplication {     var topViewController: UIViewController? {         var topViewController: UIViewController? = nil         if #available(iOS 13, *) {             topViewController = connectedScenes.compactMap {                 return ($0 as? UIWindowScene)?.windows.filter { $0.isKeyWindow  }.first?.rootViewController             }.first         } else {             topViewController = keyWindow?.rootViewController         }         if let presented = topViewController?.presentedViewController {             topViewController = presented         } else if let navController = topViewController as? UINavigationController {             topViewController = navController.topViewController         } else if let tabBarController = topViewController as? UITabBarController {             topViewController = tabBarController.selectedViewController         }         return topViewController     } } // handle any checks for any custom contollers outside of extension if let controller = UIApplication.shared.topViewController as? CPTViewController { } There is no need for the loop, waste of cpu cycles.

The Apple TV must be part of a HMHome object first, then it should be locatable under rooms of the associated HMHome Object. https://developer.apple.com/documentation/homekit/hmhome

Seeing you're producing any UI view or controllers meant for the main thread, you can run code in a background thread and just pass ima back to the main thread or write it a local disk. import UIKit import PDFKit func extractImage(completion: @escaping ((UIImage)->Void)) {     guard let path = Bundle.main.path(forResource: "filename", ofType: "pdf") else { return }     let url = URL(fileURLWithPath: path)     // Instantiate a `CGPDFDocument` from the PDF file's URL.     guard let document = PDFDocument(url: url) else { return }     // Get the first page of the PDF document.     guard let page = document.page(at: 0) else { return }     // Fetch the page rect for the page we want to render.     let pageRect = page.bounds(for: .mediaBox)     let renderer = UIGraphicsImageRenderer(size: pageRect.size)     let img = renderer.image { ctx in         // Set and fill the background color.         UIColor.white.set()         ctx.fill(CGRect(x: 0, y: 0, width: pageRect.width, height: pageRect.height))         // Translate the context so that we only draw the `cropRect`.         ctx.cgContext.translateBy(x: -pageRect.origin.x, y: pageRect.size.height - pageRect.origin.y)         // Flip the context vertically because the Core Graphics coordinate system starts from the bottom.         ctx.cgContext.scaleBy(x: 1.0, y: -1.0)         // Draw the PDF page.         page.draw(with: .mediaBox, to: ctx.cgContext)     }          DispatchQueue.main.async {         completion(img)     } } DispatchQueue.global().async {     // call extract on a global Q     extractImage { image in         // Return UIImage on main thread              } }

...

Did the shader complete calling all of the routines on another thread?

1 You're crashing on a background thread 2 This looks like it is calling a UI framework component that is meant for the main thread on the very same back thread inside a closure passed to the background thread.