“testflight the requested app is not avaliable”

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.

I use NetFSMountURLSync for my application with which I allow the user to use a custom path as a mount point (instead of /Volumes). Just to confirm, are you mounting with the no UI flag? The actual issue here is that mount points outside of /Volumes/ are now triggering a user approval dialog, which means the mount then fails if you pass in kNAUIOptionKey. Since I'm unaware of any changes, is this a bug introduced by Tahoe 26.4, or should I be using a different function to mount a network share? It's at least partially a bug (r.172210106), but I'm not sure what the parameters of the fix will actually be. In particular, the previous behavior around what was allowed here: I allow the user to use a custom path as a mount point (instead of /Volumes). ...was significantly broader than it should have been, allowing apps to target mounts that they didn't otherwise have access to or authorization from the user. Exactly what will trigger the approval dialog may continue, but at a min

Hello Giroux, miamitwinz, This is an issue we're aware of (FB22272504), but we're not aware of any recommended workaround so far. If you find something that helps you avoid the issue, please share it with the community by posting it here. Even though we're aware of this issue, we still encourage you to open a bug report, and post the FB number here once you do. The specific info you include your bug report might help our investigation, and filing the bug report you to get notified when it is resolved. Bug Reporting: How and Why? explains how you can open a bug report. Thank you for reporting, Richard Yeh  Developer Technical Support

Thanks for the post. Yes the documentation says: If a person using your app denies authorization, all attempts to schedule alarms fail. https://developer.apple.com/documentation/alarmkit/alarmmanager/requestauthorization() My question to you is, if you call func requestAuthorization() async throws -> AlarmManager.AuthorizationState when is denied, will that allow your app to request authorization again? Probably not due when the user denies a request fore authorization from the user, the system keeps that for default to avoid re-requesting the same permissions. Because the OS remembers the Deny state in the TCC database. The best approach for this in my opinion is to request an enhancement request to a reset of that privacy permissions without deleting the app from configuration. Hope this helps Albert
  Worldwide Developer Relations.

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.

Thank you for your post. We've begun investigating but we've been unable to locate your app submission to provide further assistance. Can you provide the name and App ID associated with the app? These can be found in App Store Connect in the App Information tab.