“build disappears”

@csdevfr Thank you for the recommendation. My initial message included a link to the report with the sysdiagnose. For context, here are my current setup: • TestFlight builds. • Production cards. • Apple certification stage - the step where you need to select a lab for certification. Our card provider insists that the encryption API is working as expected and that their SDK relies on the same implementation. Unfortunately, they haven’t been very responsive. I’m hoping to receive the nonces from Apple so we can confirm whether the issue is on their side and have clear evidence to ask them to thoroughly verify everything.

My iOS TestFlight build has been waiting since Feb 09. On Feb 18 I did what the Internet told me - updated the build number and reuploaded. Still waiting. Now I wonder if reuploading was a mistake. I am thinking about removing my app from TestFlight review and directly submitting for final approval, and then wait in that queue instead (which also seems to be long). I wonder if they had paused everything because of the new product launch that just happened. Only a conjecture of course.

You've set IOProviderClass to IOUSBHostDevice, but your IOKitPersonality includes the interface number, which a device doesn't have. You probably want to match against the interface (set IOProviderClass to IOUSBHostInterface) If you really want to talk to the IOUSBHostDevice, not the IOUSBHostInterface, reduce your matching criteria to include only the items in this table: https://developer.apple.com/library/archive/documentation/DeviceDrivers/Conceptual/USBBook/USBOverview/USBOverview.html#//apple_ref/doc/uid/TP40002644-BBIDGCHB The table is ancient, but still relevant. If you over-specify matching criteria, you won't match at all. You're right not to put an IOProbeScore in there. The matching process calculates an IOProbeScore (more criteria -> higher probe score). The system's driver is unlikely to be as specific as yours, so you will outmatch it anyway. The only reason to manually specify an IOProbeScore is to outmatch another driver which would otherwise have the same score based on its matching crite

How do I go about troubleshooting this? So, the place to start is actually with this log message: eventually ends with provider entitlements check failed The log message is the final, generic, error message printed by IOUserService when the entitlement check process fails. A few things to understand about what this tells you about what HASN'T gone wrong: Basic entitlement validation happens outside the kernel well before this point. So getting to this point means that your DEXT is at least somewhat coherently signed, even if it doesn't actually work. IOKit passive matching happens at the same time as entitlement checking (just before actually), so this message means that either your passive match failed or your entitlement configuration was wrong. So, the next step here is to actually take a closer look at this logging: In the logs I see the matching log entry for my driver, and it goes through some setup that mentions my driver and some entries that do not. Focusing on the entitlement checking side, each IOK

Hi @pnelson, this is Argun, Quinn's Bluetooth colleague (while I don't have a transceiver in my head, it is not for lack of trying) I have been discussing your issue with the Bluetooth team, and while we are not dismissing the possibility of a bug, it is possible that the pairing process in different app contexts are behaving differently. Except we are not able to understand what exactly the conditions are when your app works, and when it doesn't, and when it gets the one error, and when it gets the other. There are also other conditions that might effect the issue, like whether both the Mac and the phone are logged in to the same iCloud account or not (changes pairing details) To that end, we would like some more info with a sample app, and exact repro steps, and some logs. So, first please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Bluetooth for macOS and iOS to install a logging profile on each of your devices. Then, once the logging profile is instal

At least you had a reply. I have been stuck since feb 5th waiting for a review, and another app since 12th no movement. Can’t even get a TestFlight build approved to go to alpha testing. I get busy… but this is madness when I see other developers getting approvals in hours/days

Still no w word from apple unfortunately… what’s really sad is that even my external build is stuck too! even that would allow me to get some feedback. any tips for getting external builds approved?