“missing package product”

Hello everyone, I’m reaching out to see if others are experiencing an extreme delay with the App Store review process. My app has been stuck in the Waiting for Review status since February 9th, 2026. What’s concerning is that this isn't just affecting the production build for the App Store, but also a separate TestFlight External Testing submission for another project. Both have seen zero movement for over 5 weeks. Details of the situation: Submission Date: February 9, 2026. Status: Stuck at Waiting for Review (never transitioned to In Review). Communication: No messages in the Resolution Center, no metadata rejections, and no requests for additional info. Attempted Fixes: I have contacted Developer Support via the Contact Us form twice. I received a generic we are looking into it response 10 days ago, but no actual progress. Account Status: All agreements (Paid Applications, etc.) are active and signed. I’ve noticed a few other threads mentioned this specific February 9th date. It feels like submiss

On one of my machines (new MacMini M4Pro) I can’t add any new VPN configuration, doesn’t matter what I use. Trying to set up Tailscale, I get to the point where Tailscale brings up the Allow VPN configuration panel. If I hit the Allow VPN Configuration button, then macOS pops up its own panel: Tailscale Would Like to Add VPN Configurations All network activity on this Mac may be filtered or monitored when using VPN. [Allow] [Don’t Allow] I hit the allow button, and after a short wait the Tailscale panel shows in red You must allow this to use Tailscale. I can repeat this as often as I want, but Tailscale isn’t added to the VPN configurations. If I use any other third party VPN app, I get similar results: nothing gets added to the VPN configurations. If I use macOS’s System Settings and hit the Add VPN Configuration pop-up menu in the VPN section, and e.g. add an IKEv2 setup, it ask me to authenticate, and then provides me with the panel into which to put the relevant settings. I enter some test settings, and

We have a Java application built for macOS. On the first launch, the application prompts the user to allow local network access. We've correctly added the NSLocalNetworkUsageDescription key to the Info.plist, and the provided description appears in the system prompt. After the user grants permission, the application can successfully connect to a local server using its hostname. However, the issue arises after the system is rebooted. When the application is launched again, macOS does not prompt for local network access a second time—which is expected, as the permission was already granted. Despite this, the application is unable to connect to the local server. It appears the previously granted permission is being ignored after a reboot. A temporary workaround is to manually toggle the Local Network permission off and back on via System Settings > Privacy & Security, which restores connectivity—until the next reboot. This behavior is highly disruptive, both for us and for a significant number of our user

I've spent a few months writing an app that uses SwiftData with inheritance. Everything worked well until I tried adding CloudKit support. To do so, I had to make all relationships optional, which exposed what appears to be a bug. Note that this isn't a CloudKit issue -- it happens even when CloudKit is disabled -- but it's due to the requirement for optional relationships. In the code below, I get the following error on the second call to modelContext.save() when the button is clicked: Could not cast value of type 'SwiftData.PersistentIdentifier' (0x1ef510b68) to 'SimplePersistenceIdentifierTest.Computer' (0x1025884e0). I was surprised to find zero hit when Googling Could not cast value of type 'SwiftData.PersistentIdentifier'. Some things to note: Calling teacher.computers?.append(computer) instead of computer.teacher = teacher results in the same error. It only happens when Teacher inherits Person. It only happens if modelContext.save() is called both times. It works if the first modelContext.save() is com

Hi! So while Date is supported for @Parameter in an App Intent, I just discovered that Xcode will not let me use use it in a parametrized App Shortcut phrase. In my case, I would like to give the option to say today, tomorrow, or day after tomorrow for the date. Am I missing something? Any hints on the best way to approach this?

Hello, My goal is to enable users to perform a freeform search request for any product I sell using a spoken phrase, for example, Hey Siri, search GAMING CONSOLES on MyCatalogApp. The result would launch MyCatalogApp and navigate to a search results page displaying gaming consoles. I have defined a SearchIntent (using the .system.search schema) and a Shortcut to accomplish this. However, Siri doesn't seem to be able to correctly parse the spoken phrase, extract the search string, and provide it as the critiria term within SearchIntent. What am I doing wrong? Here is the SearchIntent. Note the print() statement outputs the search string--which in the scenario above would be GAMING CONSOLES--but it doesn't work. import AppIntents @available(iOS 17.2, *) @AppIntent(schema: .system.search) struct SearchIntent: ShowInAppSearchResultsIntent { static var searchScopes: [StringSearchScope] = [.general] @Parameter(title: Criteria) var criteria: StringSearchCriteria static var title: LocalizedStringResource = S

The first time that I submitted a review for my app was on February 3, 2026. It is now March 15, 2026. I am at a dead end. I have been told numerous times by Apple support to resubmit and to call back. I have a large waitlist of over 100 users that want access, and I'm only able to let my internal users test because my test flight has also not been approved. I have called Apple numerous times, being extremely respectful and explaining the situation. They then tell me to call back after 48 hours if it is not approved. I then call back and I get the exact same message. I've only had one Apple Support representative truly be honest with me and say wait a week or two because there's a backlog. I then proceeded to call back again, and was told to call back in 48 hours because they'd expedited it. I even had once a representative give me his personal information to send him a voicemail to his contact if it hadn't been completed. This then led to a dead end where he didn't respond, never responded to my voicemail, a

I have the issues in this particular guideline: Issue Description We noticed that the app requires users to register with personal information to purchase In-App Purchase products that are not account based. Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user. User registration that requires the sharing of personal information must be optional or tied to account-specific functionality. Next Steps To resolve this issue, please revise the app to not require users to register before purchasing In-App Purchase products that are not account based. You may explain to the user that registering will enable them to access the purchased content from any of their supported devices and provide them a way to register at any time, if they wish to later extend access to additional devices. Please note that although guideline 5.1.1 requires an app to make subscription content available to all the supported devices owned

Hi, my app was rejected because IAP were not present in the app. I followed guidelines more carefully and filled all buisness detail since then. And now I have: StoreKit Configuration in XCode is set to None, Products (subscription + consumable product) are already approved (from the previous review) Paid Apps Agreement - active Bank account - active Tax forms - active Compliance - active Problems: When trying to test it with TestFlight + sandbox account, StoreKit is returning zero products. When trying to check my products by initiate transaction from Sandbox App Store manage dashboard I am getting an error This item is not available I am totally stuck and don't know what to process next. Unfortunately API.