file uri scheme

After a full clean, build, and reboot, the IOServiceGetMatchingService(DriverKitAcxxx) call still fails at runtime, returning IO_OBJECT_NULL. No, it means your code is wrong and you're looking for the wrong object. From your earlier post, here is the IORegistry entry for your device: +-o DriverKitAcxxx | IOUserClass = DriverKitAcxxx | IOUserServerName = com.accusys.Acxxx.driver ... Pulling that apart in details: +-o DriverKitAcxxx This is your Service Name. In a DEX, it's set through IOService.SetName and defaults to the value of your IOUserClass. You create a match dictionary for it using IOServiceNameMatching(). IOUserSCSIParallelInterfaceController-> This is the name of the class in the kernel. It was configured by your DEX through your IOClass property, exactly as it would have been in a KEXT. You create a match dictionary for it using IOServiceNameMatching(). Making sure this is entirely clear, the class DriverKitAcxxx does NOT exist in the kernel. Instead, there is an instance of IOUserSCSIParallel

This is the response I got after submitting the appeal (2 days after submitting), but I still wasn't satisfied so I made an appeal again, but haven't made any collections Hello, Thank you for your patience while we evaluated the activity associated with your Apple Developer Program membership. We have completed our investigation and have determined that your Apple Developer Program membership, or another membership associated with your developer account, has been used for dishonest or fraudulent activity. This is prohibited by Section 3.2(f) of the Apple Developer Program License Agreement: You will not, directly or indirectly, commit any act intended to interfere with any of the Apple Software or Services, the intent of this Agreement, or Apple’s business practices including, but not limited to, taking actions that may hinder the performance or intended use of the App Store, Custom App Distribution, TestFlight, Xcode Cloud, Ad Hoc distribution, or the Program (e.g., submitting fraudulent reviews of Your own

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

@antoninb Thanks for the bug report. Please update it with a link to your AASA file and the app ID. You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.

Did anyone found a solution? I have a small update, when upgraded to Xcode 26 (instead of Xcode 16), the appclip did not build right away. The reason was Apple has changed how we need to create the .entitlements files. So I had to do the following: com.apple.developer.parent-application-identifiers - $(PARENT_APP_IDENTIFIER) + $(AppIdentifierPrefix)com.mydomain.parentID i.e add AppIdentifierPrefix + parentID instead of PARENT_APP_IDENTIFIER With this fix, the appClip got build with Xcode 26. My issue with appClip invocation is not yet fully fixed (though now it works on some cases), but hope this will give someone a starting point. Let me know if anyone found a proper solution. I have also opened a feedback and the number is FB20453270

I have a small update, when upgraded to Xcode 26 (instead of Xcode 16), the appclip did not build right away. The reason was Apple has changed how we need to create the .entitlements files. So I had to do the following: com.apple.developer.parent-application-identifiers - $(PARENT_APP_IDENTIFIER) + $(AppIdentifierPrefix)com.mydomain.parentID i.e add AppIdentifierPrefix + parentID instead of PARENT_APP_IDENTIFIER With this fix, the appClip got build with Xcode 26. My issue with appClip invocation is not yet fully fixed, but hope this will help someone. Let me know if someone found a better solution. Note: I have seen it works in some phones with iOS 26 (like iPhone 14) when I use the appClip code (circular code), but not with plain QR code, and that too not on all phones (still not works on 14 pro max). But once it works on a given phone, it worked on normal QR code too (weird, I know). My best guess is that it' a cache issue.

Seems like a known iOS 26 WKWebView bug — transitions from file:// to http:// break interactivity. Try isolating local and remote loads into separate WKWebView instances with unique WKProcessPools, or load a blank remote page before switching contexts. Apple may need to patch this in a future iOS 26.x update.

Please file a code-level support ticket with your Team ID and bundle ID for assistance.