“missing package product”

I am writing a DriverKit driver for the first that uses the USBSerialDriverKit. The driver its purpose is to expose the device as serial interface (/dev/cu.tetra-pei0 or something like this). My problem: I don't see any logs from that driver in the console and I tried like 40 different approaches and checked everything. The last message I see is that the driver get successfully added to the system it is in the list of active and enabled system driver extensions but when I plug the device in none of my logs appear and it doesn't show up in ioreg. So without my driver the target device looks like this: +-o TETRA PEI interface@02120000 | { | sessionID = 268696051410 | USBSpeed = 3 | UsbLinkSpeed = 480000000 | idProduct = 36886 | iManufacturer = 1 | bDeviceClass = 0 | IOPowerManagement = {PowerOverrideOn=Yes,DevicePowerState=2,CurrentPowerState=2,CapabilityFlags=32768,MaxPowerState=2,DriverPowerState=0} | bcdDevice = 9238 | bMaxPacketSize0 = 64 | iProduct = 2 | iSerialNumber = 0 | bNumConfigurations = 1 | UsbDev

Reading all the docs(1) I was under the impression that handling this error is well managed... Until I hit it and found out that the recommended handling options hide a crucial fact: in the catch block you can not do anything?! It's too late - everything is lost, no way to recover... All the docs mislead me that I can apply the Transcript trick in the catch block until I realised, that there is nothing there !!! This article here(2) enlightened me on the handling of this problem, but I must say (and the author as well) - this is a hack! So my questions: is there really no way to handle this exception properly? if not, can we have the most important information - the count of the context exposed through the official API (at least the known ones)? https://developer.apple.com/documentation/Technotes/tn3193-managing-the-on-device-foundation-model-s-context-window#Handle-the-exceeding-context-window-size-error-elegantly https://zats.io/blog/making-the-most-of-apple-foundation-models-context-window/

Hello everyone, I’m currently experiencing a very long review time and wanted to ask for your advice or hear about your experiences. I submitted my two apps for their initial release 23 days ago. Ever since then, they have been stuck in the Waiting for Review status. Yesterday, I realized that my Paid Apps Agreement and Tax Forms (W-8BEN, etc.) were incomplete in App Store Connect. I immediately filled them out, and now all my banking, tax, and agreement statuses are successfully marked as Active. My questions to the community are: Since the agreements are now active, will my apps automatically fall into the review queue, or do I need to trigger something? I submitted an App Review Status contact form to Apple Support today. Should I just wait for their response, or is it better to Remove from Review and resubmit them? (I am afraid of losing my place in the queue). Any insights or similar experiences would be greatly appreciated. Thank you! Best, Berkay

Our iOS & tvOS apps are stuck in Waiting for Review for several days. We have already submitted expedite review requests multiple times but received no response. This is a critical bug fix for production crash issues that affect all users. Submission IDs: iOS: 98a69297-4f1f-4a1a-80f1-6f9aa4e007bd tvOS: 4202becb-9eef-45ee-a333-de076f1bf66a Please help escalate to the App Review team. We need urgent review to fix user issues. Thank you very much.

Hello Apple Support Team, We are seeing a production crash on iOS 26 devices that appears to originate from Apple system frameworks rather than application code. 1. Crash Details OS Version: iOS 26.x App built with: Xcode 16 Devices: Multiple models (not device-specific) Exception Type: SIGSEGV SEGV_ACCERR Fault Address: 0x0000000000000100 Crashed Thread: 4 (network background queue) Crash trace summary: Last Exception : 0 libobjc.A.dylib _objc_release_x8 + 8 1 libboringssl.dylib _nw_protocol_boringssl_deallocate_options + 92 2 Network 0x000000019695207c 0x00000001968dc000 + 483452 3 libswiftCore.dylib __swift_release_dealloc + 56 4 libswiftCore.dylib bool swift::RefCounts >::doDecrementSlow<(swift::PerformDeinit)1>(swift::RefCountBitsT<(swift::RefCountInlinedness)1>, unsigned int) + 152 5 Network 0x0000000196951f6c 0x00000001968dc000 + 483180 6 Network 0x0000000196952000 0x00000001968dc000 + 483328 7 libswiftCore.dylib __swift_release_dealloc + 56 8 libswiftCore.dylib bool swift::RefC

Hello, I’m currently in the process of app notarization, but my status is stuck in the In Process state, and I’m unsure how long this should take. I’d appreciate any advice or insights. Issue Description After submitting my app for notarization, the status has been stuck in In Process for an extended period. There seems to be no progress, and it’s taking longer than I expected for the process to complete. The status hasn’t changed, and it’s been 5 days since I submitted the app. Has anyone encountered a similar issue? How long does the notarization process usually take? Any advice on how to resolve this or if there’s something I might be missing? Thanks in advance for your help!

Guideline 3.1.1 - Business - Payments - In-App Purchase The app includes an account registration feature for businesses and organizations, which is considered access to external mechanisms for purchases or subscriptions to be used in the app. Next Steps Remove the account registration features for business and organizations. Our application currently allows users to register and create multiple accounts using a phone number. All users can freely create an account. The app is designed to help users manage their own products, orders, and sales invoices. It is purely a sales management tool. We do not provide any external purchase links, external payment methods, or subscription mechanisms outside of Apple’s In-App Purchase system. However, our app was rejected under Guideline 3.1.1 with the explanation that the app includes “account registration for businesses or organizations,” which is considered access to external purchase mechanisms. We are confused about this interpretation. From our understanding

I am looking to optimize my AI-assisted workflow within Xcode. Previously, my process was inefficient: Manually selecting and copying code snippets from Xcode into Gemini. Asking a specific question (e.g., Modify this to show an alertError message box). Copying the result back into Xcode. I attempted to switch to the new native Intelligence feature in Xcode to streamline this, but I found significant shortcomings: Latency: The response time is noticeably slow. Much slower than asking directly on Gemini 3 Pro. Lack of Context: The AI often fails to grasp the full project context. For example, it frequently claims it cannot see the code for ScannerView even though it is part of the project. I often have to prompt it multiple times before it finally finds the file. Is Xcode's Intelligence feature actually production-ready yet? If not, what tools do you recommend that integrate well with iOS development? To be clear, I am not looking for vibe coding. I have a clear grasp of the problem and the high-level