“missing package product”

I’m looking for clarification on how rate limiting works for the App Attest service, especially in production environments. According to the entitlement documentation (https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.developer.devicecheck.appattest-environment), iOS ignores the environment setting once an app is distributed through TestFlight, the App Store, or Enterprise distribution, and always contacts the production App Attest endpoint. With that context, I have two questions: Rate‑Limiting Thresholds How exactly does rate limiting work for App Attest? Is there a defined threshold beyond which attestation requests begin to fail? The Preparing to Use the App Attest Service documentation (https://developer.apple.com/documentation/devicecheck/preparing-to-use-the-app-attest-service) recommends ramping up no more than 10 million users per day per app, but I’m trying to understand what practical limits or failure conditions developers should expect. Per‑AppID B

描述：低等级会员在 7 天免费期内订阅了高级会员 预期：低级会员的 7 天免费试用结束，高级会员直接扣费生效，苹果的升级通知如下： { extra_info: { quantity: 1, expiresDate: 1754627893000, purchaseDate: 1754623693000, transactionId: 2000000979349440, offerDiscountType: null, originalTransactionId: 2000000979347229, // 升级前后没有变化 subscriptionGroupIdentifier: 21729756 }, decodedPayload: {}, orgin_sku_name: unlimited.minutes.per.year.v3, payment_platform: app_store, decodedPayload_Renew: { productId: unlimited.minutes.per.year.v3, autoRenewStatus: 1, originalTransactionId: 2000000979347229 }, decodedPayload_Trans: { type: Auto-Renewable Subscription, price: 228000, bundleId: ai.plaud.ios.plaudzh, currency: CNY, quantity: 1, productId: unlimited.minutes.per.year.v3, signedDate: 1754623696459, storefront: CHN, environment: Sandbox, expiresDate: 1754627293000, purchaseDate: 1754623693000, storefrontId: 143465, transactionId: 2000000979349440, appTransactionId: 704742096472000913, transactionReason: PURCHASE, inAppOwnershipType: PURCHASED, webOrderLineItemId: 2000000107917134, origi

描述：低等级会员在 7 天免费期内订阅了高级会员 预期：低级会员的 7 天免费试用结束，高级会员直接扣费生效，苹果的升级通知如下： { extra_info: { quantity: 1, expiresDate: 1754627893000, purchaseDate: 1754623693000, transactionId: 2000000979349440, offerDiscountType: null, originalTransactionId: 2000000979347229, // 升级前后没有变化 subscriptionGroupIdentifier: 21729756 }, decodedPayload: {}, orgin_sku_name: unlimited.minutes.per.year.v3, payment_platform: app_store, decodedPayload_Renew: { productId: unlimited.minutes.per.year.v3, autoRenewStatus: 1, originalTransactionId: 2000000979347229 }, decodedPayload_Trans: { type: Auto-Renewable Subscription, price: 228000, bundleId: ai.plaud.ios.plaudzh, currency: CNY, quantity: 1, productId: unlimited.minutes.per.year.v3, signedDate: 1754623696459, storefront: CHN, environment: Sandbox, expiresDate: 1754627293000, purchaseDate: 1754623693000, storefrontId: 143465, transactionId: 2000000979349440, appTransactionId: 704742096472000913, transactionReason: PURCHASE, inAppOwnershipType: PURCHASED, webOrderLineItemId: 2000000107917134, origi

Hi everyone, We recently submitted our first B2B iOS app and had a quick question about expected review timing. The application is intended for registered wholesale clients of a food distribution company and the launch is coordinated with the rollout of our ordering platform for customers. Since the launch communication with clients is already scheduled, we wanted to confirm whether there is anything missing in the submission that could delay the review. If anyone from the App Review team can take a quick look or confirm the submission is complete, we would greatly appreciate it. App ID: 6759172913 Thank you!

I have a bunch of Audio Unit v3 plugins that are approaching release, and I was considering using subscription-model pricing, as I have done in a soon to be released iOS app. However, whether this is possible or not is not at all obvious. Specifically: The plugin can, depending on the host app, be loaded in-process or out-of-process - yes, I know, Logic Pro and Garage Band will not load a plug-in in-process anymore, but I am not going to rule that out for other audio apps and force on them the overhead of IPC (I spent two solid weeks deciphering the process to actually make it possible for an AUv3 to run in-process - see this - https://github.com/timboudreau/audio_unit_rust_demo - example with notes) Depending on how it is loaded, the value of Bundle.main.bundleIdentifier will vary. If I use the StoreKit API, will that return product results for my bundle identifier when being called as a library from a foreign application? I would expect it would be a major security hole if random apps could query a

We've been waiting since the 5th of February with zero movement, and nothing to suggest anything is likely to change. Phone support, who I've reached out to twice, has no oversight or influence, and I waited over 2 weeks for an 'automated' reply to my support request email. I'm not sure what to do... Every day that passes is momentum/money/time/enthusiasm lost. It's affecting our launch momentum and cross-platform availability for users who are expecting the iOS version to be live alongside Android, which is extremely stressful and upsetting! We would be extremely grateful if the review could be expedited so we can support our users on both platforms. If someone could tell me what, if anything, I can do to speed this up - I'd be most grateful.

I've run into what appears to be a bug in PDFKit's radio button serialization. When creating a radio button group with PDFAnnotation, only the first annotation added via page.addAnnotation() gets a correct /AS entry in the written PDF — all other annotations always get /AS /Off, regardless of buttonWidgetState. Minimal reproduction func makeRadioButton(optionId: String, isSelected: Bool) -> PDFAnnotation { let ann = PDFAnnotation(bounds: CGRect(x: 0, y: 0, width: 20, height: 20), forType: .widget, withProperties: nil) ann.widgetFieldType = .button ann.widgetControlType = .radioButtonControl ann.fieldName = Choice ann.buttonWidgetStateString = optionId ann.buttonWidgetState = isSelected ? .onState : .offState return ann } let pdf = PDFDocument() let page = PDFPage() pdf.insert(page, at: 0) // Intend to select B page.addAnnotation(makeRadioButton(optionId: A, isSelected: false)) page.addAnnotation(makeRadioButton(optionId: B, isSelected: true)) page.addAnnotation(makeRadioButton(optionId: C, isSelected: fals

Have paid for developer, have not received. I'm losing $200 a day until they doo Please help. Anyone

Hi One of the new Family Control API's requires the new Family Controls App & Website Usage capability but it appears to be missing in the latest Xcode beta (26.4 B2). MacOS and iOS all running 26.4 Beta 3. Does anyone know if we have to wait for Xcode 26.4 Beta 3 and it's associated SDK's for this one to become available?