Overview

Post

Replies

Boosts

Views

Activity

Driver Activation failure error code 9. Maybe Entitlements? Please help
This is my first driver and I have had the devil of a time trying to find any information to help me with this. I beg help with this, since I cannot find any tutorials that will get me over this problem. I am attempting to write a bridging driver for an older UPS that only communicates via RPC-over-USB rather than the HID Power Device class the OS requires. I have written the basic framework for the driver (details below) and am calling OSSystemExtensionRequest.submitRequest with a request object created by OSSystemExtensionRequest.activationRequest, but the didFailWithError callback is called with OSSystemExtensionErrorDomain of a value of 9, which appears to be a general failure to activate the driver. I can find no other information on how to address this issue, but I presume the issue is one of entitlements in either the entitlements file or Info.plist. I will have more code-based details below. For testing context, I am testing this on a 2021 iMac (M1) running Sequoia 15.7, and this iMac is on MDM, specifically Jamf. I have disabled SIP and set systemextensionsctl developer on, per the instructions here, and I have compiled and am attempting to debug the app using xcode 26.2. The driver itself targets DriverKit 25, as 26 does not appear to be available in xcode despite hints on google that it's out. For the software, I have a two-target structure in my xcode project, the main Manager app, which is a swift-ui app that both handles installation/activation of the driver and (if that finally manages to work) handles communication from the driver via its UserClient, and the driver which compiles as a dext. Both apps compile and use automated signing attached to our Apple Development team. I won't delve into the Manager app much, as it runs even though activation fails, except to include its entitlements file in case it proves relevant <dict> <key>com.apple.developer.driverkit.communicates-with-drivers</key> <true/> <key>com.apple.developer.system-extension.install</key> <true/> <key>com.apple.security.app-sandbox</key> <true/> <key>com.apple.security.files.user-selected.read-only</key> <true/> </dict> and the relevant activation code: func request(_ request: OSSystemExtensionRequest, didFailWithError error: any Error) { // handling the error, which is always code value 9 } func activateDriver() { let request = OSSystemExtensionRequest.activationRequest(forExtensionWithIdentifier: "com.mycompany.driver.bundle.identifier", queue: .main) request.delegate = self OSSystemExtensionManager.shared.submitRequest(request) //... } And finally the Manager app has the following capabilities requested for its matching identifier in our Apple Developer Account: DriverKit Communicates with Drivers System Extension On the Driver side, I have two major pieces, the main driver class MyDriver, and UserClient class, StatusUserClient. MyDriver derives from IDriverKit/IOService.iig but (in case this is somehow important) does not have the same name as the project/target name MyBatteryDriver. StatusUserClient derives from DriverKit/IOUserClient.iig. I have os_log(OS_LOG_DEFAULT, "trace messages") code in every method of both classes, including the initializers and Start implementations, and the log entries never seem to show up in Console, so I presume that means the OS never tried to load the driver. Unless I'm looking in the wrong place? Because I don't think the driver code is the current issue, I won't go into it unless it becomes necessary. As I mentioned above, I think this is a code signing / entitlements issue, but I don't know how to resolve it. In our Apple Developer account, the Driver's matching identifier has the following capabilities requested: DriverKit (development) DriverKit Allow Any UserClient (development) DriverKit Family HID Device (development) -- NOTE: this is planned for future use, but not yet implemented by my driver code. Could that be part of the problem? DriverKit Transport HID (development) DriverKit USB Transport (development) DriverKit USB Transport - VendorID -- submitted, no response from Apple yet HID Virtual Device -- submitted, no response from Apple. yet. This is vestigial from an early plan to build the bridge via shared memory funneling to a virtual HID device. I think I've found a way to do it with one Service, but... not sure yet. Still, that's a problem for tomorrow. Apparently I've gone over the 7000 character maximum so I will add my entitlements and info.plist contents in a reply.
10
0
312
2d
touchesEnded: not triggered on newer iOS when view is inside UIScrollView (was working on iOS 18)
Hi everyone, I’m facing an issue with touch handling on newer iOS versions. I have a custom view controller implemented in Objective-C that overrides touchesEnded:. The same code works correctly on iOS 18, but on newer iOS versions (tested on iOS 26), touchesEnded: is no longer being triggered. Important observations: touchesBegan: is triggered. touchesEnded: is NOT triggered. touchesCancelled: is also NOT triggered. No code changes were made between iOS 18 and iOS 26. Same code, same sample works fine in iOS18 device but not in iOS26 device Questions: Has gesture arbitration behavior changed in recent iOS 26 versions when views are inside UIScrollView? Any clarification on whether this is intended behavior or a regression would be greatly appreciated. Thank you.
Topic: UI Frameworks SubTopic: UIKit
6
0
251
2d
13 days in "Waiting for Review" – is this normal now?
Submitted my app update 13 days ago. Status hasn't changed from "Waiting for Review" even once. Not a single message from Apple. I know reviews can take time, but 13 days stuck in waiting queue feels extreme for a minor bug fix update. Usually takes 1-2 days for me. Anyone else seeing these wait times lately? Should I do something or just keep waiting? Getting worried something is wrong with my submission.
2
0
66
2d
Longer than usual wait time?
Hello, We submitted a v1 of our app in December, it took a day to review. The v1 was just a test version to make sure Apple were happy with it. We submitted v1.1 last Friday (20th) and are still sat in "Waiting for Review" - I can see a fair few other people are waiting, but does anyone know the reason why? Our launch is tied to national and trade press, which we're now going to have to push back at cost to the business. Any advice from anyone? App ID is 6753305041 Thanks
2
0
62
2d
App review stuck, since 12th Feb
Hi, I know many of us are stuck right now it seems - I'm in the 12th Feb club (had another app that was since 5th, I've since pulled that and resubmitted Monday this week, to see if things might have unstuck themselves, but no luck) I can't even get a build approved for TestFlight on anything. This is getting silly now, total lack of communication - emails go unanswered. I will give the lovely team in Ireland their dues though, as always helpful on the phone, but they also seem to have no information and their expedited review requests go no where. App ID is 6758779640
2
0
77
2d
iOS 26: default gray background on UITabBarItem
In iOS 26, when a UITabBarItem is selected, a gray background appears behind the selected item. This seems to happen automatically with the new tab bar design. I tried configuring the tab bar using UITabBarAppearance, but the background highlight still appears. Is this the expected behavior in iOS 26 or is there a recommended way to configure the tab bar so that only the icon and title change color when selected?
Topic: UI Frameworks SubTopic: UIKit
2
0
88
2d
MapKit Snapshot API returning blank dark blue images — started today
Issue: MapKit Snapshot API returning blank dark blue images instead of satellite tiles as of March 4, 2026. This is affecting production and we need urgent assistance. Endpoint: snapshot.apple-mapkit.com/api/v1/snapshot Symptoms: HTTP 200 response with a valid image file, but image is a solid dark navy frame with only the Apple Maps watermark — no satellite data. Occasionally a correct satellite image is returned, but the vast majority are blank. Parameters: t=satellite, 640x640. Confirmed not caused by code changes (none made), auth errors or rate limiting (status is 200), or an invalid image format (image is well-formed, just blank). API keys have been rotated and the issue persists. The intermittent correct responses suggest a backend tile-serving issue on Apple's side rather than anything client-related. Started: March 4, 2026. Same requests that worked prior to this date now consistently fail. Please see the attached sample images for reference. ASAP resolution is appreciated as this is actively impacting production. Thanks, Tristan
3
1
113
2d
stuck in “Waiting for Review” since February 22
Hello Apple Developer Support, My app has been stuck in “Waiting for Review” since February 22, and I have submitted multiple inquiries without receiving any response. This delay has now become extremely concerning. Missing a planned launch due to an indefinite review timeline is very difficult for independent developers. If there is an issue with the submission, I would appreciate clear communication. If there are review delays, transparency would help us plan accordingly. I respect the review process, but the lack of updates after this amount of time is frustrating. I would sincerely appreciate clarification on the status. I just want to present my application to everyone more quickly. Apple ID: 6759447148 Thank you.
2
1
96
2d
Persistent 1-year delay and stagnation in "Waiting for Review" after Expedited Approval - Beezzy - Agenda Digital
Hello, My app, Beezzy - Agenda Digital, had an Expedited Review request approved recently (confirmation received via email). However, the status remains stuck in 'Waiting for Review' for an unusual amount of time, even for an expedited process. This update is critical for our operations and addresses urgent fixes. Has anyone else experienced a delay between the expedited approval and the actual 'In Review' transition lately? Is there any additional step required from the developer side to trigger the priority queue? App ID: 6751509489 Thank you for any guidance.
1
0
36
2d
SpriteKit framerate drop on iOS 26.3
Hello, I have noticed a performance drop on SpriteKit-based projects running on iOS 26.3. The issue seems very similar to the issue reported on iOS 26.0, and later solved from iOS 26.2 beta 3: https://developer.apple.com/forums/thread/800952?answerId=870617022#870617022 With 26.3, it seems a regression occured. Below is the same SpriteKit scene used to test framerate on different devices: import SpriteKit import SwiftUI class BareboneScene: SKScene { override func didMove(to view: SKView) { size = view.bounds.size anchorPoint = CGPoint(x: 0.5, y: 0.5) backgroundColor = .darkGray let roundedSquare = SKShapeNode(rectOf: CGSize(width: 150, height: 75), cornerRadius: 12) roundedSquare.fillColor = .systemRed roundedSquare.strokeColor = .black roundedSquare.lineWidth = 3 addChild(roundedSquare) let action = SKAction.rotate(byAngle: .pi, duration: 1) roundedSquare.run(.repeatForever(action)) } } struct BareboneSceneView: View { var body: some View { SpriteView( scene: BareboneScene(), debugOptions: [.showsFPS] ) .ignoresSafeArea() } } #Preview { BareboneSceneView() } Running this very basic spritekit scene on my device and I can not reach an FPS of 60. Instead, it stalls around 40. I see the same in my AppStore published SpriteKit games. As you can see in the discussion of the linked forum topic, the regression has been noticed by others as well. Can you please look into this, and let us know if there is an outstanding action to resolve it already? It's very problematic for published games suddenly dropping to 40FPS on even the most modern iOS devices.
3
3
427
2d
Account pending
Hi everyone, I purchased an Apple Developer Program membership about three days ago. The payment has already been successfully charged to my bank account, but my account is still showing the status “Pending” with the message “Subscribe your membership.” I haven’t received any confirmation email or any request for additional information since completing the purchase. I’m curious if others have experienced a similar delay recently, and how long it took before your developer account was fully activated. Any insights or experiences would be greatly appreciated. Thanks in advance!
2
2
606
2d
Where can I check Non-Renewing Subscription purchase history in Sandbox?
Hello, I am currently testing In-App Purchases for my app in the Sandbox environment. Our app has two types of products: Auto-renewable subscriptions Non-renewing subscriptions When testing auto-renewable subscriptions, I can see the subscription in the Sandbox account management screen, and I can perform actions such as: Viewing the active subscription Cancelling the subscription Upgrading or downgrading the subscription However, when testing non-renewing subscriptions, I cannot find the purchase history anywhere in the Sandbox account management screen. Because of this, I cannot verify whether the non-renewing subscription purchase was recorded correctly. My question is: Where can I check the purchase history for Non-Renewing Subscriptions in the Sandbox environment? Is there a specific place in: App Store Connect Sandbox account settings Or somewhere else where these purchases can be reviewed? Thank you in advance for your help.
1
0
26
2d
Core data destroyPersistentStore, not working for some
Hi all I have a problem with core data, where when a new user login that is different from the previous user i delete all of core data by using "destroyPersistentStore". Then i recreate the persistent store, this works when i am testing. When it does not work for one of my users when she test. I am not sure why this should not work, i have added the code i use to destroy the persistent store below. This code is run after login but before the view changes away from my login view. // Retrieves the shared `AppDelegate` instance guard let appDelegate = UIApplication.shared.delegate as? AppDelegate else { return } appDelegate.destroyDataSyncBackground() // Get a reference to a NSPersistentStoreCoordinator let storeContainer = appDelegate.persistentContainer.persistentStoreCoordinator // Delete each existing persistent store for store in storeContainer.persistentStores { if let url = store.url { do { try storeContainer.destroyPersistentStore( at: url, ofType: store.type, options: nil ) } catch { print("Failed to deleted all") } } else { print("Failed to deleted all") } } // Re-create the persistent container appDelegate.persistentContainer = NSPersistentContainer( name: "CueToCue" // the name of // a .xcdatamodeld file ) // Calling loadPersistentStores will re-create the // persistent stores appDelegate.persistentContainer.loadPersistentStores { (store, error) in // Handle errors let description = NSPersistentStoreDescription() description.shouldMigrateStoreAutomatically = true description.shouldInferMappingModelAutomatically = true appDelegate.persistentContainer.persistentStoreDescriptions = [description] } // Reapply context configuration let viewContext = appDelegate.persistentContainer.viewContext viewContext.automaticallyMergesChangesFromParent = true viewContext.mergePolicy = NSMergeByPropertyObjectTrumpMergePolicy do { try viewContext.save() appDelegate.recreateDataSyncBackground() } catch { print("Debug: saving delete all failed.") } } The function "destroyDataSyncBackground" just set the my sync class to nil so stop any changes to core data while the code is running. The function "recreateDataSyncBackground" recreate the sync class so fetch, post and patch requests is made again.
3
0
58
2d
“Breaking the Throughput Ceiling for Deterministic Mobile Registries?”
log Results(using my own SIR(0.0)Lengua Canonical host programming language using Swifty Complier) 14 Billion Operations on an iPhone 12: The SIR(0.0)Lengua Benchmark The Accomplishment I have successfully benchmarked a "bare-metal" implementation of the SIR+Nexus protocol on an iPhone 12 (A14 Bionic). I am currently seeking funding/grants to move from this high-performance core into a full production-ready registry ecosystem. If you are interested in supporting a project that brings supercomputer-grade verification to the edge, I’d love to connect ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:46:13 +0000 🔁 NONCE: CBECB308-2E3C-48FA-989D-AD129E27A74C ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772815573.139092 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0013537406921386719 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 2 Actions per Engine: 7000000000 Cores: 2 Execution Time: 41.30783951282501 seconds Total Executed Canons: 14000000000 Throughput: 338918717 canons/sec Checksum: 17979805505785589248 ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:40:18 +0000 🔁 NONCE: 6968F42F-5646-4DE9-BCD4-02F6D53426E2 ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772815218.9165797 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0014863014221191406 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 1 Actions per Engine: 7000000000 Cores: 2 Execution Time: 40.646605491638184 seconds Total Executed Canons: 7000000000 Throughput: 172216103 canons/sec Checksum: 18213274789747570432 ===================================l ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:26:21 +0000 🔁 NONCE: 83BFC05F-9582-4EDF-8154-7FC88A925CE7 ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772814381.243969 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0013855695724487305 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 591428 Actions per Engine: 7000000000 Cores: 2 Execution Time: 41.8350967168808 seconds Total Executed Canons: 14000000000 Throughput: 334647248 canons/sec Checksum: 17979805505785589248 ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:33:17 +0000 🔁 NONCE: 808B2B4D-A69A-4062-B2BC-D546B0DCBCAA ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772814797.3462362 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0014896392822265625 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 590 Actions per Engine: 7000000000 Cores: 2 Execution Time: 41.28380227088928 seconds Total Executed Canons: 14000000000 Throughput: 339116051 canons/sec Checksum: 17979805505785589248 ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:18:13 +0000 🔁 NONCE: B8B6575E-DBB3-44C4-95D2-D7D22DC87075 ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772813893.3843408 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0014749765396118164 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 64 Actions per Engine: 512 Cores: 2 Execution Time: 15.000059366226196 seconds Total Executed Canons: 4791923200 Throughput: 319460282 canons/sec Checksum: 160388065465600 ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:21:29 +0000 🔁 NONCE: 4C5E58E7-CC42-487C-A972-00666A6DA78A ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772814089.8965917 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0014749765396118164 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 590 Actions per Engine: 70000 Cores: 2 Execution Time: 15.00032925605774 seconds Total Executed Canons: 5049660000 Throughput: 336636610 canons/sec Checksum: 23152360350731280 ✅ CANON INGESTED Identity: SIR(0.0)Lengua Version: v1.0.0 🔐 HASH: 7affcfc92e1fcfff 📜 NOTARIZED AT: 2026-03-06 16:22:42 +0000 🔁 NONCE: 8B8125E3-71EB-43FB-8DB5-9749192C2C9D ✍️ SIGNATURE: SIR(0.0)Lengua|v1.0.0|8863031054657638399|1772814162.3418667 🌐 NAMESPACE: sir://SIR(0.0)Lengua/7affcfc92e1fcfff First ingest latency: 0.0013689994812011719 seconds =================================== 🔥 CANON STRESS TEST COMPLETE Identity: SIR(0.0)Lengua Engines: 590 Actions per Engine: 700000 Cores: 2 Execution Time: 15.00326406955719 seconds Total Executed Canons: 5138700000 Throughput: 342505469 canons/sec Checksum: 235609058415150000
0
0
186
2d