“missing package product”

Thanks for reporting the issue. The error indicates that HealthKit lost the cached data source information, which is an implementation detail inside the framework. Do you have a feedback report yet? If not, would you mind to file one with a sysdiagnose, and share your report ID here? You can following the instruction here to install the profile and capture a sysdiagnose from a device that reproduces the issue. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Did I miss a step in uploading the build? Unless you explain what a thing that you so-call 'build' is and where and how you uploaded it, nobody can really give you a definite answer.

Same here on Vision Pro. Reinstalled everything on a clean headset with same results: “This app can't run and must be verified.” Lost 4 hours!!

Same error, for ~2hrs now. But curl returns successful, confusingly. curl -v https://ppq.apple.com Host ppq.apple.com:443 was resolved. IPv6: (none) IPv4: 17.33.192.136, 17.33.193.105, 17.33.194.109 Trying 17.33.192.136:443... Connected to ppq.apple.com (17.33.192.136) port 443 ALPN: curl offers h2,http/1.1 (304) (OUT), TLS handshake, Client hello (1): CAfile: /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/certifi/cacert.pem CApath: none (304) (IN), TLS handshake, Server hello (2): (304) (IN), TLS handshake, Unknown (8): (304) (IN), TLS handshake, Certificate (11): (304) (IN), TLS handshake, CERT verify (15): (304) (IN), TLS handshake, Finished (20): (304) (OUT), TLS handshake, Finished (20): SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384 / [blank] / UNDEF ALPN: server accepted h2 Server certificate: subject: CN=ppq.apple.com; O=Apple Inc.; ST=California; C=US start date: Jan 21 17:47:41 2026 GMT expire date: Feb 17 18:28:16 2027 GMT subjectAltName: host ppq.ap

I've gotten OK, Bad-Gateway, Gateway Time-Out on four different systems. Even when OK is returned, it takes a while to get a response. This started almost exactly at 10am pacific time for me. Like many of you I used the security command line to check my certs, checked my firewall (PFSense), and even switch my build system and my target iPad to use my iPhone personal hot-spot, in order to bypass my infrastructure and still, no-joy. After reading your posts, I have become convinced that this is an Apple services issue, even though their status page says everything is working. More information. I have another project (Project-B) I'm working on, which is being developed on a different machine. Project-B installs on the same target iPad with no issues. I migrated the failing project (Project-A) over to this machine and added the missing certificates to the keychain so that the failing project would build. Even on this second system, I'm consistently getting the error for project-a but not for project-b. S

Hello, Thank you for the clarification, and we appreciate the time and guidance. We understand from the documentation that when submitting subscriptions for the first time, they must be submitted together with a new app version and must be in “Ready to Submit” status before doing so. However, we appear to be encountering a repeat issue related to the submission flow in App Store Connect. On our app version page, the “Select In-App Purchases or Subscriptions” / “Add In-App Purchases” control referenced in the documentation is not available, so we are unable to attach the subscriptions to the version in the way described. From what we can see in our App Store Connect interface, the UI appears to follow the newer submission flow, where subscriptions are configured on their own product pages and are automatically bundled with the app submission. Because of this, there is no option on the version page to manually add or select subscriptions. This has resulted in a repeated loop where the app build is subm

Thanks for the reply Quinn. We've spent the time looking into the options you suggested. Am I right in assessing that each needs some level of code modification of the app under test? We're reluctant to add test hooks that would end up in released product, esp networking code, because this app is a medical device that already has FDA trial approval based on SBOM documentation showing no networking libraries (and thus a low cybersecurity risk rating), and no operating differences between tested and released .ipa files. Modifying the iPad's environment is kosher which is why the helper app was helpful.

By the way guys if you are chillin out here, have you seen new Ferrari's presentation with the Jony Ive? Do you agree Jony brings back those wow product vibes again? https://www.youtube.com/watch?v=BhVjIw9cv_4

Same issue on my end. We have thousands of iPads not being able to load Production app that users rely on for their business. This is crazy.

Hello, When submitting an In-App Purchase or subscription for the first time, you must submit it with a new app version. You can check the details on how to do this on the docs, specifically on the Submit an In-App Purchase for the first time section: https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase Please review the docs and let me know if you've already tried the listed steps. Also, make sure that your In-App Purchase or subscription has the Ready to Submit status before submitting it for review. If it hasn’t, check if there is any missing information: https://developer.apple.com/help/app-store-connect/manage-in-app-purchases/view-and-edit-in-app-purchase-information

The location UIBackgroundModes key is specific to the startupdatingLocation() API that allows the app to run uninterrupted in the background, and is not necessary for the low energy APIs like significant location and region monitoring. This is what the review feedback meant as well: If the app does not require persistent real-time location updates, please remove the location setting from the UIBackgroundModes key. Indeed, the documentation you quoted says If your iOS app must keep monitoring location even while it’s in the background, use the standard location service and specify the location value of the UIBackgroundModes key to continue running in the background The standard location service mentioned here is the API I mentioned above which uses continuous GPS locations. I should also point out that the document you have referred to is an old archived document from 2016, and while some of the information might still be valid, there could be missing changes, and definitely the modern location APIs a