does your iPad support anything other than mirroring? See https://support.apple.com/guide/ipad/connect-to-a-display-with-a-cable-ipadf1276cde/18.0/ipados/18.0 Also, you need a touchpad or mouse, because otherwise you can't manipulate windows on the external screen. And you might need an external keyboard too.

it works for me (M1 MBA and M1 MBP with M1 Pro). If I were you, I'd file a bug, then delete Xcode 26b5 and everything associated with it, then re-install it. If that doesn't work, and you're on a beta of macOS, wipe the Mac and reinstall everything. If it is still a problem, follow up on the bug with new crash logs. If it is fixed, close the bug with "cannot reproduce".

and here are the bug numbers FB19449747 No developer flavor of PCI transport capability FB19450162 Two indistinguishable PCI transport capabilities shown FB19450508 Xcode hides provisioning profiles FB19451832 indistinguishable USB transport entitlements also, to revert the changes you made to a victim machine: sudo nvram boot-args -c to clear all the boot-args. sudo nvram boot-args --help will tell you more then boot into recovery and perform csrutil enable to turn SIP on again

thank you Kevin for that answer. In the meantime I've discovered a few more facts, which I'll detail here. I'll also file some bugs and attach their numbers here. I did manage to get a PCI driver to match and install on a victim machine. I used an Xcode-generated profile that includes our own PCI entitlement, but installed the driver on a machine with entitlement checks turned off. To do this, on the victim machine: boot into recovery and turn SIP off (csrutil disable at the command line) boot back into the OS, and execute: sudo nvram boot-args="amfi_get_out_of_my_way=1 -arm64e_preview_abi dk=0x8001" reboot to let the boot-args take effect change the architecture of the driver to arm64e (it was ${STANDARD_ARCHS} (in build settings/architectures) It is possible that not all of the boot-args are necessary. I had to change the build architecture because it seems like the other arguments make the OS think that everything is a platform binary. The driver still failed entitlement checks until I added dk=0x8001. All of this information takes a lot of searching to find (some of it comes from these very forums) I then tried making a USB driver for development (for a vendor ID we don't have an entitlement for). On my usual Mac, the driver won't load because the entitlement in my provisioning profile is for a specific vendor ID - I can't choose the development USB transport capability. I would have to deploy this driver on a victim machine with SIP off and the same shenanigans as above. This probably wouldn't affect a team with no USB transport entitlement at all, they'd only be able to choose the development flavor of the capability.

some code accessed a nil pointer. The code doesn't belong to your process (or else you would have landed in the debugger with a BAD_ACCESS error), instead didStop is called. However, almost undoubtedly your code caused the nil pointer access. Take a close look at how you manage video buffers and read the documentation very carefully. CMSampleBufferCreateCopy doesn't actually copy the buffer's data, for example.

what type of object is a ScreenStreamOutput? I don't see it anywhere in Apple's documentation. I'd expect your app, or a component thereof, to conform to SCStreamOutput protocol. So it should implement a func stream( _ stream: SCStream, didOutputSampleBuffer sampleBuffer: CMSampleBuffer, of type: SCStreamOutputType ) that's where you'd put logic which copies the content of the sampleBuffer into your private circular buffer.

sudo xcodebuild -license run it in an empty directory so it doesn't actually build anything. More info in the man page for xcodebuild.

the timestamp part of "pre-sign" varies from one implementation or invocation to the next - does it have to? I suggest you use a fixed string for the timestamp value for all programs and then look at the requests in Wireshark to see what the differences are.

I think you're using the wrong certificate type. "Developer ID Application" is for applications. Developer ID Installer is for .pkg files.

Please don't use the Comments feature to reply to posts (they don't open by default and watchers don't get notifications for them). Mac apps are bundles, directories with a well-known format and a .app extension. They appear to Finder as single files. If you are building with Xcode, the submission process begins with Archiving, not Building. You Archive your app (Product menu), then open the Organizer (in the Window menu), select the archive you just made, and click Distribute Content. To learn more, begin here https://developer.apple.com/macos/submit/. If you are building with some other tool, you'd be better off asking your question on a forum specific to that tool.

you are right, you can't define multiple interface numbers within one IOKitPersonality. But you can define multiple IOKitPersonalities. IOKitPersonalities is a dictionary of dictionaries. The keys are strings (which can be anything meaningful to you, the OS doesn't care what they are), each value is a dictionary. Copy your dictionary which matches against bInterfaceNumber=1, and modify it to match against bInterfaceNumber=2. I believe the rules outlined still apply. https://developer.apple.com/library/archive/qa/qa1076/_index.html

Don't post it here, nobody will take action. File bugs using Feedback Assistant. That's what beta releases are for.

There's not much to go on here - tell us which specific file is missing, from what?

The entitlements file looks okay. Remember, the vendor ID is a decimal number. I suggest that you install your app and driver on a Mac. There are more tools available to debug with, and you can add code to explicitly load and unload the driver, while on iPadOS that process is completely automatic. Are you using the same version of iPadOS now as you were using with the working (development version) of the driver? One version of iPadOS didn't show the Driver toggle in Settings, I don't remember which.

You sent the same comment seven times, which probably nobody read. I'm not sure what the comments feature is for; new comments don't bump the visibility of a thread, and they're closed by default. You haven't said what sort of accessory your peripheral is. If it is mass storage, a microphone, a camera, a keyboard or a game controller, there is native support for such devices on iOS. If it is something else, you need some kind of custom software. On iPhone, (and on many models of iPad), you cannot use DriverKit, so your only recourse is EAP and making your device part of the MFi program.