missing package product

Hello everyone, I’m looking for advice from developers who may have faced a similar situation, as we appear to be stuck in a long-running loop of Guideline 4.3(a) rejections on iOS with no actionable feedback from App Review. Over an extended period, our iOS app has been repeatedly rejected under Guideline 4.3(a) (“similar or repackaged”), regardless of the changes we make. The responses from App Review consistently use the same high-level language and do not indicate what specifically is considered problematic. Some relevant context: The app is built with Flutter using a single shared codebase. The macOS version, built from the same codebase with the same overall structure and UI, has been approved without issues. The iOS version, using that same implementation, continues to receive 4.3(a) rejections. We do not use purchased templates and do not operate multiple developer accounts. Like most apps, we use some third-party and open-source components where technically appropriate. Across multiple submissions, w

Hi all, I'm encountering an issue with auto-renewable subscription upgrades in the App Store. Here's my setup: Context: Plan A: Base Plan (yearly auto-renewable subscription) Plan B: Pro Plan (monthly auto-renewable subscription) B is configured as an upgrade from A. Issue: When a user with an active Plan A subscription upgrades to Plan B, I correctly receive an App Store Server Notification v2 with DID_CHANGE_RENEWAL_PREF and UPGRADE subtype. According to Apple's documentation, a prorated refund is issued automatically in this scenario, and no separate REFUND event is sent, the refund information should be retrievable through the upgrade event itself. Testing in Sandbox: In my sandbox tests, Plan A has a 1-hour duration and Plan B has a 5-minute duration. After the user upgrades to Plan B, I immediately cancel the subscription to prevent auto-renewal. Expected vs. Actual Behavior: After the 5 minutes expire, Plan A still appears as the active current entitlement. I initially thought this might be because the

Hello everyone, I’m looking for advice from developers who may have faced a similar situation, as we appear to be stuck in a long-running loop of Guideline 4.3(a) rejections on iOS with no actionable feedback from App Review. Over an extended period, our iOS app has been repeatedly rejected under Guideline 4.3(a) (“similar or repackaged”), regardless of the changes we make. The responses from App Review consistently use the same high-level language and do not indicate what specifically is considered problematic. Some relevant context: The app is built with Flutter using a single shared codebase. The macOS version, built from the same codebase with the same overall structure and UI, has been approved without issues. The iOS version, using that same implementation, continues to receive 4.3(a) rejections. We do not use purchased templates and do not operate multiple developer accounts. Like most apps, we use some third-party and open-source components where technically appropriate. Across multiple submissions, w

I'm struggling to implement required code for SB2420 compliance. I try to learn on a very simple use case. the app is UIKit Build in Xcode 26.2 it displays a single Hello view with a button that will simply show a Good day label. I assume the app will be rated 4+. I tried the following code, using available information in Xcode (limited): import UIKit import DeclaredAgeRange // other import needed ? class ViewController: UIViewController { @IBOutlet weak var welcomeLabel: UILabel! // initially hidden override func viewDidLoad() { super.viewDidLoad() // Do any additional setup after loading the view. } func testAgeRange() -> Bool { if !isEligibleForAgeFeatures { // Not found. Which import needed ? return true // Not called from Texas } // Following code from Xcode doc… do { let response = try await AgeRangeService.shared.requestAgeRange(ageGates: 13, 15, 18) // Compiler Error: Missing argument for parameter 'in' in call // Can I add the 4 gate ? guard let lowerBound = response.lowerBound else { //

So I'm seeing a 'Pending User Info' for the paid apps agreement, and I'm not sure why as I just signed it. Why am I getting this message? For context, I'm currently working on my app and the IAP product(using sandbox to test it). So I can't test my product until the this is active. Not sure what to do.

Hello, My app uses auto-renewable subscriptions. I submitted an update and at first the subscription products appeared properly under the monetization section in App Store Connect. However, after resubmitting the binary for review, the subscription product attachment disappeared, and now it is not possible to re-attach them. Even sandbox testing cannot retrieve the subscription identifiers anymore, because the monetization section no longer shows the products. Questions: Why did the subscription products disappear after a resubmission? How can I re-attach subscription products to the new version? Do I need to remove the current version submission to make subscriptions appear again? Does App Review need to finish processing subscription approval separately? Notes: The first version binary showed subscription products. After internal rejection and resubmission, they disappeared. Using StoreKit 2 restore flow in production code. Sandbox accounts cann

AgeRangeService is the burning topic right now. Needless to say, Everything is so unclear. We got our app finally into the TestFlight for QA and the product to test. only to find out that AgeAssurance for sandbox testing does not work. There is no document confirming or denying whether and when age assurance for the App with the release configuration in test flight would work. There isn't any guidance from Apple on whether an app that sells physical goods, such as an e-commerce app, can continue doing business as usual. Also, there is no clarity that the Age assurance options are off, 13, unverified, 13 verified, and so on. How those should be used.

During internal testing, we observed the following behavior and would appreciate clarification on whether it is expected and supported in production environments. When generating an elliptic-curve cryptographic key pair using kSecAttrTokenIDSecureEnclave, and explicitly specifying a kSecAttrAccessGroup, we found that cryptographic operations (specifically encryption and decryption) could be successfully performed using this key pair from two distinct applications. Both applications had the Keychain Sharing capability enabled and were signed with the same provisioning profile identity. Given the documented security properties of Secure Enclave, backed keys, namely that private key material is protected by hardware and access is strictly constrained by design, we would like to confirm whether the ability for multiple applications (sharing the same keychain access group and signing identity) to perform cryptographic operations with the same Secure Enclave–backed key is expected behavior on iOS. Specific

Hello, According to documentation, the App Store does not re-download the entire app when updating, but instead generates an update package containing only the changed content compared to the previous version. I’d like to clarify the following points: 1. Granularity of file changes If only part of a large file changes, does the update package include the entire file, or does it patch only the modified portions within that file? 2. Guideline on separating files The documentation recommends separating files that are likely to change from those that are not. How should this be interpreted in practice? 3. Verifying the diff result Is there a way for developers to check the actual diff result of the update package generated by the App Store without submitting the app? Is there a diff command tool or comparison method closer to the actual App Store update process? 4. Estimating update size during development For apps with large-scale resources, minimizing update size is critical. Are ther

where can i get apple's all device hardware vid and pid ?