missing package product

@Ja239 my subscriptions and business agreements are all approved If the status of your subscriptions is Approved in App Store Connect, review their availability in App Store Connect. Confirm you select all the countries or regions where you want to sell the In-App Purchases. For more information, see TN3188: Troubleshooting In-App Purchases availability in the App Store. Yet, when the paywall in my app appears, and someone clicks the subscribe button to pay, the IAP isn't appearing. It just loads forever. For more information, see TN3188: Troubleshooting In-App Purchases availability in the App Store. When I tested in Xcode it just kept saying products not found. Id's are the same, bundle id is the same, ive done everything. If your app fails to display its products when testing In-App Purchases in Xcode or the Apple sandbox environment, see TN3185: Troubleshooting In-App Purchases availability in Xcode and TN3186: Troubleshooting In-App Purchases availability in the sandbox, respectively.

@hungta The Ready to Submit status indicates that you uploaded all the metadata needed, but you have not yet sent it to Apple for review. For Sandbox testing, is this status expected, or do we need to submit an app build or the generic product for review before Advanced Commerce works correctly? Testing In-App Purchase in the Apple sandbox environment doesn’t require you submit your In-App Purchases for review as mentioned in TN3186: Troubleshooting In-App Purchases availability in the sandbox. Continue testing in the sandbox, then submit your produce for review once you are satisfied. For more information about submitting In-App Purchases, see Submit for review.

The product status ready to submit pertains to submitting your product identifiers to the App Store review process for live deployment. This status is not applicable during sandbox testing or TestFlight phases, you are free to test when they are submitted or not. In terms of being enabled for Advanced Commerce, If you have submitted your generic product identifiers to the program, then you are now waiting for them to notify you when your products are enabled for Advanced Commerce. At this juncture, you can commence your sandbox and TestFlight testing. Then when you are prepared to release your app to customers, you will submit your updated app and these generic IAP products to the App Store review process. For further information on submitting your product identifiers to the App Store, please refer to the following link: https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase

The following console log says that your app detected an account switching at the beginning of the launch process, which may erase the existing data created before the switching. It also says that you were using a simulator. CoreData: warning: CoreData+CloudKit: -[PFCloudKitSetupAssistant _checkUserIdentity:]_block_invoke_3(1487): : CKIdentity record has changed from _b09f3f2b1357d21fdd823f58762f6077 to _4e8dc229775b034192825a3081a709a4 error: CoreData+CloudKit: -[NSCloudKitMirroringDelegate _performSetupRequest:]_block_invoke(1242): : Failed to set up CloudKit integration for store: (URL: file:///Users/yuanping_ke/Library/Developer/CoreSimulator/Devices/BA9191E9-6DB4-4A30-9196-0A6C06A11F2E/data/Containers/Data/Application/5977FE0D-50D4-4AE0-8134-5D8B0B662298/Library/Application%20Support/default.store) Later your app did successfully set up CloudKit integration, as shown below, and then did several successful exports and imports, but it seems that there is no change merged into the store. CoreData: warning:

Thank you for sharing your post. I find it intriguing, but I am unable to replicate the functionality you have described on my own devices. The code works the same in all simulators I have tried. The parent SwiftUI view is a List, which is destroyed when nested view presentations and alerts are involved. While you mentioned that it works correctly on other simulators and devices, I have consistently encountered the same issue when running it on different simulators with the same configuration. I would personally implement a custom mechanism to manage when and how the sheet is presented, potentially using a combination of state flags and conditional views to avoid relying on the immediate modifier behavior or better, do not include inside a List that will be destroyed. I am still very interested in knowing what device and versions of iOS the code: List { VStack { LibraryView(title: “Show view (Loss of state)”) } } works so that I can investigate the reason, in my case, the state did not work in any si

Thanks for the post, this is very interesting. And thanks for the bug where includes the focused project sample. Navigating complex hierarchies in SwiftUI while maintaining state can indeed be challenging. I can try to suggest some potential workarounds and strategies to mitigate state loss issues during navigation and app backgrounding but I also want to see this issue and use your focus sample to see how the sheets are lost after being presented on the app and to see if moving state management to a parent view is the answer and understand how the views are not being shown after the background. Passing state down through view hierarchies can ensure it's retained longer than if it were localized in deeply nested views. If you're not already on the latest SwiftUI and iOS version, consider updating to see if the issue has been addressed in more recent releases. Additionally, beta versions can sometimes provide pre-release fixes. You can see the status of your feedback in Feedback Assistant. Th