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.

short answer is yes. Longer answer is at this link: https://developer.apple.com/support/compare-memberships/

The area on the left in grey is called the "navigator" You've selected the Find navigator, and you expect to see files containing text containing "readNumber". You're searching in an area called "macOS" (selected using the popup underneath the search field. I don't know what that is - it isn't one of the pre-defined search scopes. I usually use "in Project" or "in Project & SDK". In addition, if you look at the bottom of the Find navigator, there's a file name filter. Your search doesn't find "readNumber" at all, so this doesn't make any difference here, but I have no idea where it is searching. Clear the file filter at the bottom and change the search scope to "project" and see if it works then. Also, select the Project navigator, expand the project view and post the screenshot - it should looks something like this if it doesn't, maybe we'll be able to help you out. Incidentally, clearly Xcode is finding something, because it built and ran your program. Also, if you're new to this, why are you building for both macOS and iOS? It would be easier to start with just one.

Hi. In future, please post error messages as text, not screen shots, they're a lot easier to view that way. Somehow you have almost every file in your target twice. If you're new to Xcode, this could be quite difficult to fix. If you don't want to go that route, open the target in Xcode, select the Build Phases tab, and check the Compile Sources, Link Binary With Libraries and Copy Bundle Resources phases. Remove any duplicate entries. You may find it helpful to create a new, minimal project in Xcode from its iOS app template, so that you can compare a working target with your own.

I suspect most folks who develop for their personal use are using Xcode, that's why you're not seeing much of a response. You can develop an app using a personal developer account and deploy it to your own phone. In Xcode, you select "automatic" signing under your own personal team. Xcode will put the app on your phone. It will work for a week I think before you need to build and deploy it again. I don't know how you handle this if the app is built and signed in some other workflow. But there is an Xcode menu item under its Window menu, called "Devices and Simulators". Your phone should show up there, if you've ever used it for development. There's a list of installed apps there, with a little "+" button underneath - you should be able to select your app built with third party tools and send it to your phone. If your phone doesn't show up in the list, build one of the template apps for iOS in Xcode, then plug your phone in and select it as a run destination. Xcode should prompt you to put your phone in developer mode. After you've done this, your phone should appear in the list of available Devices (even if it is only available over WiFi).

yes to splitting up views into smaller chunks. They can be easier to test that way. I've often pasted non-working code into Copilot and asked "why doesn't this compile?". LLMs are quite good a pointing out errant commas and the like, where a compiler will often give you an entirely logical, but useless error message (unless you write compilers for a living).

use the Reply feature for replies. No notifications are sent to watchers if you add a comment. How about changing the window's transparency? See https://developer.apple.com/forums/thread/694837 (I haven't tried this, just kicking ideas around)

Have you considered using hide and unhide on the app instead? If you don't want the user to close the window, you could suppress the appearance of the close button using .windowDismissBehavior(.disabled) in macOS 15 and later.