@edford Could you share the code for the example in the video? I tried to use blendMode but it didn't work for me.

I can confirm that the issue still exists. Just released a new app that uses SubscriptionStoreView(groupID: "someGroupId"). I tested on Simulator and Test Flight, there were no issues at all. After the app is approved and released, I got a message from a user who was complaining about the "Subscription unavailable" screen on my app. I didn't test my app after the release because I thought if everything works on Test Flight, there shouldn't be any issues on the App Store. After the message, I installed the app and got the same error. Then, I implemented the change, SubscriptionStoreView(productIDs: ["someProductId1", "someProductId2"]) and submitted a fix this morning. The app is just approved, I installed the new version and the store page works now. It is really sad that Apple is not acknowledging this issue and trying to fix it. I shared my app yesterday on LinkedIn and my landing page got hundreds of visitors. Probably I missed a lot of sales because of the bug in the StoreKit API. I guess from now on, I will need to test my app not only on Test Flight but also on the App Store. @SPEEDCUP thank you for sharing the workaround!

I'm having the same issue. I tested my app both on Simulator and TestFlight successfully but the review team can't see the in-app purchases. I'm just using one line of code to show my products (StoreView(ids: ["tipTiny", "tipSmall", "tipMedium", "tipLarge"])). It is obvious to me that there is a bug in StoreKit.

I'm having the same "Cannot use staged migration with an unknown model version." error for my app on production. I started with an unversioned SwiftData model with iCloud, then released a new version for my app that puts the same model inside of V1 and also have a lightweight migration to V2. Now, all the users are complaining about the crash on launch. I spent a day to find a solution for the issue but unfortunately the only solution is deleting the app and installing it again. Looks like Apple is not willing to admit this issue and fix it. Therefore, I highly suggest people who use SwiftData to start with versioned schema. Or if you already shipped an unversioned schema, first put your model into a versioned schema and release a new build for your app. Wait for most of your users to update to that build. Then, create another release that includes your migration. These are the only ways to avoid the crash on launch. It is good that I used iCloud so nobody lost their data.