+1Same issue, newly uploaded and "ready" TestFlight build(s) show up successfully in App Store Connect but not in the TestFlight app for install, and no invitations for new build(s) sent.[Someone suggested rebooting target device(s), however that didn't help in my situation; still no success with installing "ready" TestFlght builds. I've also just now contacted support.]

Agree, wasted a few hours until I found this thread. TestFlight showing "green" at Apple's status page.

Same, still NOT working.Status at App Dev status site says resolved, however new binaries are still labeled as "ready" at App Store Connect portal but don't show up in the TestFlight app.

A couple. of threads about this.Currently Apple's status page still shows an issue with the TestFlight service, but no explanation and no ETA as to when it will be fully resolved.

Also experiencing these issues (slow typing, slow navigation) with XCode13. Albeit, my app is incredibly complex, multiple files, many containing thousands of lines of code. But XCode is a professional tool, and hasn't given me this kind of grief in the decade using it to build for the Apple eco system. If this continues it may finally push me away from Apple development and move my work to "web applications" instead. PS Unchecking Preferences->General->Show Live Issues helped but didn't completely solve the slowness issues for me.

Same issues as everyone else, i.e. recently migrated to M1 MacBook Air and paste no longer works in iOS 15.4 Simulator. I downloaded 13.7 simulators as suggested, paste works in 13.7 but now (in 13.7) certain kinds of videos (streams) refuse to load. Xcode 13.3; running in Rosetta mode (using some libraries e.g. AFNetworking that aren't yet updated/supported w/ new M1). Any new insights into (fixing?) this issue appreciated.

Same issue, re: iPhone mini 12; I get screen dimensions of 375x812 (x3) reported in the Simulator. Whereas the actual device dimensions are 360x780 (x3). This basically renders it impossible for me to account for iPhone mini 12 as you've said without having a physical device.

Same. Thought it was on my end and wasted a few hours removing and reinstalling certificates and provisioning profiles. Would be nice if Apple's Status web page actually reflected these issues with an accurate status )-:

Same purple warning in Xcode 14 here. "This method should not be called on the main thread as it may lead to UI unresponsiveness." In my case I've traced it to a WKWebView -> loadRequest:, i.e. called from my main ViewController's -> viewDidLoad: I load a web view at app startup, as after launch/splash screen it's the first view user will see. I'm careful about accounting for network issues and will timeout (or not even try loading), display an alternative screen, etc. if there are network issues. I'm going to assume someone on the Xcode team chose to add this warning in the event a developer doesn't account for slow loading or not loading at all an initial wkwebview when the app first launches? Any other theories? Is it safe to ignore the warning?

Same purple warning in Xcode 14 here. "This method should not be called on the main thread as it may lead to UI unresponsiveness." In my case I've traced it to a WKWebView -> loadRequest:, i.e. called from my main ViewController's -> viewDidLoad: I load a web view at app startup, as after launch/splash screen it's the first view user will see. I'm careful about accounting for network issues and will timeout (or not even try loading), display an alternative screen, etc. if there are network issues. I'm going to assume someone on the Xcode team chose to add this warning in the event a developer doesn't account for slow loading or not loading at all an initial wkwebview when the app first launches? Any other theories? Is it safe to ignore the warning?

Same purple warning in Xcode 14 here. "This method should not be called on the main thread as it may lead to UI unresponsiveness." In my case I've traced it to a WKWebView -> loadRequest:, i.e. called from my main ViewController's -> viewDidLoad: I load a web view at app startup, as after launch/splash screen it's the first view user will see. I'm careful about accounting for network issues and will timeout (or not even try loading), display an alternative screen, etc. if there are network issues. I'm going to assume someone on the Xcode team chose to add this warning in the event a developer doesn't account for slow loading or not loading at all an initial wkwebview when the app first launches? Any other theories? Is it safe to ignore the warning?

Same purple security warning in Xcode 14 (latest release) here. "This method should not be called on the main thread as it may lead to UI unresponsiveness." In my case I've traced it to a WKWebView -> loadRequest:, i.e. called from my main ViewController's -> viewDidLoad: i.e. I load a web view at app startup, as after launch/splash screen it's the first view user will see. I'm careful about accounting for network issues and will timeout (or not even try loading), display an alternative screen, etc. if there are network issues. I'm going to assume someone on the Xcode team chose to add this warning in the event a developer doesn't account for slow loading or not loading at all an initial wkwebview when the app first launches? Any other theories? Is it safe to ignore the warning?

Same issue in all 16.4 Simulators, HLS video is black, audio is fine. Tested on e.g. 14.1 simulators and the video plays as it should. What's weird is this (16.4 simulators) was working fine until today and I'm pretty certain I've not updated since a few weeks ago (all automatic updates are off).

We're discussing this same issue over here too: https://developer.apple.com/forums/thread/727288

Interestingly, the pixels from an HLS stream are available in the 16.4 Simulator(s), i.e. it's possible to get a valid (loaded w/ the video frame and not black) CVPixelBufferRef from the stream, even though video won't display on screen. Att: Apple, please hurry up with a fix on this! It makes developing streaming video applications a pain i.e. not being able to actually program and text the latest OS on anything other than connected devices (rendering the Simulators pretty much useless for developing our application).