Mine are also getting stuck in "Processing" for hours. Developer Support was able to clear the last two that were stuck. Attempted to upload another build, and it cleared processing, but in the AppStoreConnect TestFlight tab it doesn't show either "Manage Compliance" or "Ready to Submit" and is not available as an Internal TestFlight build (102802106402). These issues began at around 9p last night and I haven't been able to get a build through without help from developer support since then. I suspect they're getting a lot of requests for help because their phone system isn't working either--you get the outbound call but it doesn't respond to touchtone menu inputs (and now the schedule page throws an error). I've noticed that happening in the past when there are widespread issues with build processing.

Very late reply, but just for anyone else I use the following: { BOOL isAppOnMac = NO; if (@available(iOS 14.0, *)) { isAppOnMac = [NSProcessInfo processInfo].isiOSAppOnMac; } return isAppOnMac; }

I'm seeing the same issue on some devices, both iPhones and iPads, running the production release of iOS/iPadOS 17.0.2. I thought that perhaps this issue was only with [HKHealthStore isHealthDataAvailable], so as a test I tried bypassing that call and proceeding with the call to [healthStore requestAuthorizationToShareTypes:], wrapped in a try/catch block. The authorization check though just throws an exception indicating the same error, that "Health data is unavailable on this device", so internally, the auth request API is still calling [HKHealthStore isHealthDataAvailable]. The issue doesn't appear on all devices, most seem to work. I have customers with multiple devices and it will work on one but not the other; in some cases it's their iPhone that doesn't work, and in others it's their iPad running iPadOS 17. I've tried going into the Health App to make sure I've gone through its initial setup in case that was the issue, but it had no effect. The next step is to create a simple app that demonstrates the problem and submit that to Apple with a bug report, but I've done this in the past and waited years with no resolution or response from Apple. Were you able to resolve the issue or have you discovered anything else?