missing package product

I'd like to report an issue with the App Referrer source segmentation in the App Store Connect Analytics API. Issue Summary When retrieving impression data via the App Store Connect Analytics API using groupBy=[sourceType, sourceInfo], the impressions attributed to specific referring apps (e.g., Facebook, Instagram) do not match the values displayed in the App Store Connect web dashboard. Details The total impressions in the API and dashboard are completely consistent, with the report category: App Store Discovery and Engagement Standard_Daily. The aggregated App Referrer (overall category) is also consistent. However, the detailed segmentation data in App Referrer is inconsistent, with the report category: App Store Discovery and Engagement Detailed_Daily. For example: The web dashboard shows significantly more impressions attributed to Facebook or Instagram. The API returns fewer impressions for the same referral source. Furthermore, the API does not return any unknown/other referral source entries, and dis

StoreKit ask to buy should have more data in pending state. When user try to purchase ask to buy, we should get at least transactionID, product itself, and time that user start the request. So we can keep track of the whole transaction flow jwsRepresentation should always available for every state, actually even failing state. And should attach state inside of it. Instead of only available after verified purchase. So we can use transactionID and everything relate to transaction for both waiting for purchase and Currently we only have jwsRepresentation after complete purchase, which is very limited its usage

I would like to inquire about the originalTransactionId of StoreKit2. Users who purchase auto-renewal subscription products To re-purchase the same subscription item after cancellation and prior to refund If you receive a refund after cancellation and re-purchase the same subscription item If you do not renew immediately after expiration and re-purchase the same subscription after a long period of time I would like to ask if 1, 2, and 3 all use the same value as the original Transaction Id at the initial subscription. In the case of 3, if you re-purchase more than a few days after the last subscription purchase, please let me know if there are any detailed conditions such as the original Transaction Id not maintained.

I've been thinking of bringing some older games back to the modern Mac. Rewriting old titles in Swift but using the original data files that assume use of non-rounded corners Windows. Many of these games require all the Window space of a 90 degree cornered Window. Can anyone point me at some useful workarounds or Is Apple simply deaf to the needs of this type of product?

Hi, I’ve added attestation to my app, and everything worked as expected during setup. However, after deployment, I noticed some unknownSystemFailure entries in the production logs on New Relic. Could you help me understand what typically causes this error? The documentation suggests issues such as failing to generate a token. What scenarios could lead to that?

Hello, My app MyCourses (bundle id: com.ahmedbaqer.mycourses) was rejected under Guideline 2.1 because No action followed when we tapped the button to subscribe to a course on iPadOS 26.1. When I run the same code (version 1.0.0 (11)) from Xcode on a real device using a StoreKit configuration file (In App Purchase.storekit), the purchase flow works correctly: When I tap the Subscribe via Apple button, the App Store purchase sheet appears. The purchase completes successfully and unlocks the course. I use the in_app_purchase Flutter plugin and queryProductDetails to load products. However, when I install the build via TestFlight (and in App Review), tapping the same Subscribe via Apple button does nothing – which matches the behavior described by App Review. From my logs it looks like queryProductDetails is returning an empty productDetails list in that environment. For In‑App Purchases: I created 7 non‑consumable products in App Store Connect. Their Product IDs exactly match the IDs

Unable to notarize Electron-based application. All notarization attempts fail with The signature of the binary is invalid for main executable and Electron Framework, despite passing local codesign verification. ENVIRONMENT: macOS: 24.6.0 (Sequoia) Hardware: Apple M4 Max (arm64) electron-builder: 26.0.12 Electron: 36.9.5 (also tested 37.10.2, 38.2.0) Certificate: Developer ID Application: AS LIVE MEDIA SP Z O O Team ID: 2KJ532SU3G Certificate validity: Oct 7 2025 - Oct 8 2030 PROBLEM: Every notarization submission fails with identical error for two binaries: Contents/MacOS/PresentClic Desktop Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework Error message: The signature of the binary is invalid. Architectures affected: Both x86_64 and arm64 CRITICAL CONTRADICTION: ✅ Local verification PASSES: $ codesign --verify --deep --strict PresentClic Desktop.app Result: valid on disk, satisfies Designated Requirement ❌ Apple notarization service FAILS: Error: The signature of the binary is in

Hello everyone, I recently submitted my new app “Bitcoin Miner – Mining Pool” for App Review. The app was submitted under my Apple Developer account (Account Holder: Harshil Patel). However, the status has been “Waiting for Review” for over 2 days without any movement. Details: Submission platform: App Store Connect Metadata & screenshots uploaded correctly No compliance warnings or “Missing Information” alerts No previous rejections for this version I understand the review process time may vary, but I’m unsure whether this delay is normal or if there’s something more I should check on my side. Questions for the community / Apple Team Is there a typical timeline for apps currently showing “Waiting for Review”? My only goal is to ensure the submission process is moving correctly. Any guidance or suggestions will be highly appreciated. Thank you! — Harshil Patel

Hello everyone, I recently submitted my new app “Bitcoin Miner – Mining Pool” for App Review. The app was submitted under my Apple Developer account (Account Holder: Harshil Patel). However, the status has been “Waiting for Review” for over 2 days without any movement. 📍 Details: Submission platform: App Store Connect Metadata & screenshots uploaded correctly No compliance warnings or “Missing Information” alerts No previous rejections for this version I understand the review process time may vary, but I’m unsure whether this delay is normal or if there’s something more I should check on my side. 👉 Questions for the community / Apple Team Is there a typical timeline for apps currently showing “Waiting for Review”? My only goal is to ensure the submission process is moving correctly. Any guidance or suggestions will be highly appreciated. Thank you! — Harshil Patel

Hi all, I’m currently testing an auto-renewable subscription whose availability is restricted to Japan only (all other territories disabled in App Store Connect). However, when testing in the Sandbox environment, the behavior does not match the availability settings: Sandbox Apple ID storefront: Taiwan Subscription availability: Japan only StoreKit 2 (Product.products(for:)) still returns the product Sandbox purchase succeeds even though it should be unavailable in this region. Questions Is this expected behavior in the Sandbox environment? Does Sandbox not enforce subscription territory availability? Is this a known limitation where Sandbox validates the purchase flow only, without applying real storefront availability rules? Will territory restrictions be enforced correctly in production once the app and subscriptions are “Ready for Sale”? Is there any recommended way to test storefront-based availability before release? Thanks in advance!

Hello, I noticed the Product.SubscriptionInfo subscriptionPeriod (of type Product.SubscriptionPeriod) is different for the same product between StoreKit Testing in Xcode and the sandbox/App Store (production) environment. For a “1 week” auto-renewable subscription, we get the following: StoreKit Testing in Xcode: 1 week gives a subscriptionPeriod with value of 1 and a unit of Product.SubscriptionPeriod.Unit.week Sandbox/App Store: 1 week gives a subscriptionPeriod with value of 7 and a unit of Product.SubscriptionPeriod.Unit.day This created issues in my app because I used the localizedDescription of a Product.SubscriptionPeriod to display a text similar to “$4.99 per week”. This is what I obtain with the StoreKit Testing in Xcode, but in the Sandbox/App Store environment, it displays “$4.99 per day” (because the subscriptionPeriod is “7 Days” and the unit is then .day). Obviously, this is not what I wanted to display. Other periods like “1 month”, “2 months”, “3 months”, “6 months, and “1 y