“testflight the requested app is not avaliable”

In relation to the OP experience, since a few weeks, my app also has received an unprecedented amount of SIWA user complaints indicating they are not getting our emails. Investigation on a subset of these feedbacks have ruled out user error (spam, outdated redirect email address). Like OP, we're always getting a success response code when submitting emails to Apple's relay server. I had opened an issue in feedback assistant a few weeks ago: FB22012678 Are you still able to investigate the case of need one with fresher logs? FYI I've been using SIWA for several years, and something clearly started to happen a few weeks/months ago. Thank you

Distribution through the App Store requires a minimum deployment target of iOS 15. The Xcode Support webpage has this information.

Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.

Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.

A quick test shows it uses the xattr-specific ES events. Not definitive, and may differ on some systems, but this was one of the affected devices. Is that all of the events you got for that target? It is deleting xattrs, but none of those are the rsrc fork. My best guess is that this was cleanup work just prior to the remove() call that actually hung. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.

First off, as a general note, I've done my best to answer your questions below, but what I'd actually like to understand is what your larger product goal actually is, independent of any particular technology (like DriverKit). My concern here is that you're focusing on DriverKit because it's one of our more visible technology layers and then asking how it can solve your problem... without ever realizing that there are other API options that would actually be a far better solution. As a concrete example of this, I regularly see questions from developers trying to write DEXTs for vendor-specific USB devices who don't realize that the RIGHT way to work with a vendor-specific USB device on macOS is the IOUSBHost framework. intercept raw HID input reports from an external mouse through any top case–related path in the HID stack. This is the first time I've heard the term top case, but from the general context, I'm going to guess that your goal is to intercept and modify the events 3rd-party HID devices are sending

If your app has been rejected and you need help resolving the issue, consider taking advantage of one of the following support options available from App Review: Request a call with an Apple representative to discuss the outcome of the review. Make this request in the App Store Connect communication. Submit an appeal to the App Review Board if you believe your app follows the App Review Guidelines. Visit the Contact Us page on Apple Developer and select the App Review tile to learn more.

Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.