“xcode github”

Thank you for your response, I appreciate you taking the time to clarify. Just to make sure I fully understand: does this mean there is no possibility that the submission could be evaluated in Xcode if needed, or would that decision be up to the review team? Thanks again for your help.

Also saw these warnings now in the xcode cli Warnings: Failed to locate resource named default.csv CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000 IOServiceOpen failed: 0xe00002e2 IOServiceOpen failed: 0xe00002e2 IOServiceOpen failed: 0xe00002e2 IOServiceOpen failed: 0xe00002e2

Nevermind. After rebuilding / uploding (this time with Xcode Cloud), and sending a friendly email to the devteam, my app got approved. Not sure if it was the rebuild or the email what did it.

That’s what was happening last night 😅 Currently (on the latest beta), I always get that error when trying to activate the TestFlight build. However, some testers have reported being able to activate 🤷‍♀️ But (still on the latest beta) versions installed from Xcode eventually activate. They flip many times between “busy” and “error” before tho, but that’s not new. It takes like a minute for the NEURLFilterManager.Status to eventually go to running. Once it does, everything works. I don’t see any new errors on the server side, always the same two that were already common two days ago when everything was working, so I don’t think these are related, but here goes anyway: Gateway: 2026-03-03T13:01:21.886520Z ERROR ThreadId(02) http_request{request_id=508c3c86-e2e2-440b-901e-0041f5928152 method=POST uri=/gateway user_agent=unknown}: ohttp_gateway::handlers::ohttp: Failed to decapsulate OHTTP request: a problem occurred with HPKE: Failed to open ciphertext PIR: 2026-03-03T12:50:16+0000 error id=8836ee445

So, currently I implemented a small POC app with content filtering and it seems to be working fine when I run it through Xcode. But as I uploaded the app to test flight then I do not see any setting related to content filtering in the Settings App or can not see any kind of permission alert for filtering. Same behaviour for ad hoc build as well. So what should we do in this case ?

OK, so for some reason, the provisioning profile includes the USB entitlement for vendorID= and I thought because I requested a specific vendor id that I only get that. So after putting into the vendor id field in my USB entitlement in Xcode, they now match, and it works. Strange.... These are the development only entitlements. See this forum post for a detailed run-through of the codesigning side of this. In terms of the matching side of this: The comments feature of the forums is not particularly useful, so please post a complete copy of your IOKitPersonalities dictionary, posted using the code option (which makes it easy to copy out). I have a rundown of the matching and loading process here, so please start by reviewing and validating your DEX against that. That document specifically covers this: Should I set something else for IOClass if my driver does bind to USB interfaces and takes care about exposing them as USB serial devices to the os? I currently have IOClass=IOUserService Also mentioned

By watchOS standalone app, did you mean watch-only app, with the terminology defined in TN3157? For a watch-only app, it does seem that Xcode 26.x doesn't provide the App Store Connect option in the app archiving process, which, to me, is likely a bug. Do you have a feedback report yet? If not, would you mind to file one with screenshots that show the steps you use to create and archive a project, and then share your report ID here? Thanks. Best, —— Ziqiao Chen  Worldwide Developer Relations.

First, I wanted to apologize for not replying for a full month, as well as thank you very much for your reply. I was pulled away from this project for a couple weeks, and when I got back I was still spinning my wheels getting the driver installed. Not a problem at all. It was 67 characters and, apparently the maximum is 63. Seems like an arbitrarily short max in this day and age, and you'd think both XCode and the Developer Portal would catch that, but that's what it was. Sigh... I'm sorry I didn't think of that, as I'm aware of that limitation and actually posted about it here. FYI, you should also be aware of the version number limitation described here, which is another arbitrary restriction the kernel enforces. So, on to my current problem. The driver installs... but doesn't load. Probably because it's not matching. So I'm going to give more detailed information in the hope you can help me with this. If you haven't seen it already, I have a post here that does an extended run down of the matching