“missing package product”

Hi developer community, First time iOS developer here. I originally submitted my iOS app for review on Friday February 20th and was asked to make a small change on Monday February 23rd, which I did promptly and resubmitted with a new build that evening. It's been a week since I resubmitted and wondering if I may have done something incorrectly when reattaching a new build to the review submission. I requested an expedited review on Friday February 27th and contacted support this morning but haven't seen any movement on the waiting in review status yet. My app is highly dependent on seasonality (winter sports) and I missed a key opportunity at an event last week to promote the app while the app has been stuck in review. Any guidance or assistance would be super welcome so I can get my app out into the world before we get into the Spring season! App ID: 6759411804 Thanks

100% new here, and probably trying to jump the gun here. I've released my 1st build to TestFlight for some people to test, but till now the app is still under review. Does it always take this long (day 4 now) for a 1st build to be reviewed, or am I missing something here?

Context: I am building an iOS productivity app using EAS Build. The project has 4 targets: the main app and 3 extensions (ShieldAction, ShieldConfiguration, ActivityMonitorExtension). The Issue: I have officially received approval from Apple for the Family Controls (Distribution) entitlement for my main Bundle ID. However, the build still fails during the Xcode phase. The Errors: Xcode reports that the generated provisioning profiles do not include the com.apple.developer.family-controls entitlement. For example: Provisioning profile *[expo] com.*.** AdHoc 177247892.... doesn't support the Family Controls capability. All 3 extensions are failing with the exact same error. What I've done: Confirmed approval from Apple for com.*.**. Enabled Family Controls and App Groups on the Apple Developer Portal for all 4 Identifiers. Cleared EAS local and remote cache using eas build --clear-cache. Deleted existing profiles on both Expo.dev and Apple Portal to force regeneration. The Question: Even with official

the iOS app store package's entitlements file has an issue. After updating to a new version to fix the entitlements file, the app still crashes upon opening but can function normally after a restart. What methods can the app side use to resolve this entitlements file issue without requiring a restart to open and use the app properly?

I am using official MCP SDK. According to official guide, Servers MUST provide structured results that conform to this schema. https://modelcontextprotocol.io/specification/draft/server/tools#output-schema I could see output schema defined, but result have no structured content. Current output schema: { name: XcodeListWindows, title: List Windows, description: Lists the current Xcode windows and their workspace information, inputSchema: { type: object, properties: { }, required: [ ], }, outputSchema: { type: object, properties: { message: { description: Description of all open Xcode windows, type: string, }, }, required: [ message, ], }, } Current response: { result: { content: [ { type: text, text: {message:* tabIdentifier: windowtab1, workspacePath: xxxn* tabIdentifier: windowtab2, workspacePath: xxxn}, }, ] } } Expected: { result: { content: [ { type: text, text: {message:* tabIdentifier: windowtab1, workspacePath: xxxn* tabIdentifier: windowtab2, workspacePath: xxxn}, }, ], structuredContent: { message: *

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.