“testflight the requested app is not avaliable”

We are trying to intercept raw reports from the built-in MacBook haptic trackpad using a DriverKit IOUserHIDEventDriver dext. Our dext installs and activates successfully: OSSystemExtensionRequest finishes with result 0 systemextensionsctl list shows the dext as activated enabled the dext is embedded correctly in the app bundle However, it never attaches to the built-in trackpad IOHIDInterface. ioreg shows the built-in trackpad interface still matched only by Apple’s HID dext. We also observed that Apple’s own HID dext appears to use com.apple.developer.driverkit.builtin, while that entitlement is not available in our provisioning profile. Our dext specifically relies on: IOUserHIDEventDriver::handleReport(...) SetProperties() with kIOHIDEventDriverHandlesReport Questions: Is com.apple.developer.driverkit.builtin required for a third-party IOUserHIDEventDriver to match a built-in internal trackpad IOHIDInterface? Is that entitlement public/requestable, or Apple-internal only? At wha

Hello, I hope you’re doing well. I recently submitted an update for my app, and I would really appreciate it if you could review it when possible. The latest version includes important fixes and improvements. Please let me know if anything else is needed from my side. Thank you for your time and support.

Hi everyone, I am experiencing a strange rendering issue on iPadOS 26 when sizeRestrictions.minimumSize is set on a UIWindowScene. After rotating the device and then rotating it back to the original orientation, the window appears to be stretched based on its previous dimensions. This resulting stretched area does not resize or redraw correctly, leaving a significant black region on the screen. Interestingly, as soon as I interact with the window (e.g., a slight drag or touch), the UI snaps back to its intended state and redraws perfectly. Here is a sample code and capture of behavior. class SceneDelegate: UIResponder, UIWindowSceneDelegate { var window: UIWindow? func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) { guard let windowScene = (scene as? UIWindowScene) else { return } windowScene.sizeRestrictions?.minimumSize = CGSize( width: 390, height: 844 // larger than the height of iPad in landscape ) // initialize... } } Has an

Hi everyone, I recently got rejected under Guideline 1.1.1 - Safety - Objectionable Content and I'm struggling to understand how my app falls under this category. Looking for advice from anyone who's dealt with similar rejections. What the app does: AutoSignal is a vehicle notification app designed for the Bulgarian market. It solves a very common real-world problem - needing to contact a car owner when their vehicle is double-parked, blocking you in, has its lights left on, or has been hit/damaged while parked. The core flow is: A user scans a license plate using their phone camera If the car owner is registered in the app, they receive an anonymous push notification (e.g., Your car with plate XX 1234 XX is blocking someone or Your lights are on) The car owner can then take action Users can also report vehicle damage cases with temporary witness notes that auto-expire after 7 days. Why I believe it doesn't violate 1.1.1: The app does not expose any person

Hello everyone, I’m looking for some clarification and advice regarding an unexpected App Review rejection under Guideline 4.1 – Copycats. My app has been live on the App Store since May 2024, and during that time, it has maintained the same core flow, structure, UI, and feature set. There have been no major redesigns or attempts to imitate any other app. Recently, I submitted a new version (v3.2) with only minor changes related to ad logic implementation (no UI/UX changes, no branding changes, no metadata changes). However, this update was rejected with the following reason: “This app or its metadata appears to be misrepresenting itself as another popular app or game…” This has left me quite confused for a few reasons: The app has been approved and publicly available for nearly 2 years There were no significant design or branding changes in this submission The rejection seems unrelated to the actual ch

Note: This document is specifically focused on what happens after a DEXT has passed its initial code-signing checks. Code-signing issues are dealt with in other posts. Preliminary Guidance: Using and understanding DriverKit basically requires understanding IOKit, something which isn't entirely clear in our documentation. The good news here is that IOKit actually does have fairly good foundational documentation in the documentation archive. Here are a few of the documents I'd take a look at: IOKit Fundamentals IOKit Device Driver Design Guidelines Accessing Hardware From Applications Special mention to QA1075: Making sense of IOKit error codes,, which I happened to notice today and which documents the IOReturn error format (which is a bit weird on first review). Those documents do not cover the full DEXT loading process, but they are the foundation of how all of this actually works. Understanding the IOKitPersonalities Dictionary The first thing to understand here is that the IOKitPe

I've been unable to enroll in the Apple Developer Program and am posting here after exhausting the standard support channels. The situation: When I attempt to enroll in the Apple Developer Program as an individual, I receive the error: Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. No additional explanation is provided. I have contacted Apple Developer Program Support multiple times by both phone and email. Each time, I was told there is nothing they can do. I asked for escalation and was told escalation is not possible. At no point was I given a specific reason for the rejection. One possible cause I identified on my own is that the name on my developer profile may not match my legal name. My Apple ID at appleid.apple.com shows my correct legal name, but I'm unsure whether my developer profile reflects the same. I have not been able to confirm whether this is actually th

Hello all Synopsis: document based SwiftData app breaks document handling after first save due to internal error saving the -shm file. Long: i am working on a small document based SwiftData app for macOS. The UI works well as long as the document was not saved. After saving the document and reopening it, I get an error consistently in console: BUG IN CLIENT OF libsqlite3.dylib: database integrity compromised by API violation: vnode unlinked while in use: /Users/vrunkel/Library/Containers/de.ecoobs.CurtailmentAnalyzer/Data/tmp/TemporaryItems/NSIRD_CurtailmentAnalyzer_mrXKMs/NewDocument/StoreContent-shm So somehow the -shm file is still referenced to NewDocument created when the app opens an untitled document and resides in the temporary folder. I have saved the document to my documents folder. After reopening and the above error deletion or addition of items crashes the app with a long backtrace to view updating: Modifications to the layout engine must not