I would like to encourage continued posting of updates and new developments here, even though the feedback reports have been closed. By doing so, we provide a valuable source of information for others. This will enable us to gather comprehensive data on why the issue persists and why it doesn't work as intended. While we've found a workaround using other APIs to get the storefront working, the reliability of these methods has not been fully tested. This solution does not address the root problem and should not lead us to accept a non-functional API that is expected to work correctly. The most significant concern is that the issue appears in the App Store, despite functioning properly in Xcode and TestFlight. It is likely that many app developers are unaware that their storefront isn't loading. Let’s continue to collect and share updates to ensure that the SubscriptionStoreView API, which utilizes the groupID initializer, is finally addressed and fixed by Apple.

I would like to remind everyone to share all future findings and updates in our existing forum post. While we've found a workaround using other APIs to get the storefront working, the reliability of these methods has not been fully tested. This solution does not address the root problem and should not lead us to accept a non-functional API that is expected to work correctly. It is crucial to continue sharing updates and new insights in the forum post, along with all relevant information. This will enable us to gather comprehensive data on why the issue persists and doesn't work as intended. The most significant concern is that the issue appears in the App Store, despite functioning properly in Xcode and TestFlight. It is likely that many app developers are unaware that their storefront isn't loading. Let’s continue to collect and share updates to ensure that the SubscriptionStoreView API, which utilizes the groupID initializer, is finally addressed and fixed by Apple.

Additionally, a brief update on the feedback reports submitted by Thomssie and myself. After thorough investigations and multiple attempts to resolve the issue, despite reports from other users experiencing the same problem, the report was closed. We have been diligently working for weeks to find a solution, consistently sharing our updates and findings in this forum post, as well as in the bug report. However, it appears that the issue is not being addressed further due to a claim of "insufficient information." To verify the error, it would suffice to use either my app or Thomssie's app. The issue is evident in the previous version (v1.0), where the storefront fails to load, while the new version (v1.1), utilizing the SubscriptionStoreView API with the productIDs initializer (docs), functions correctly as of now. As a result, we are left without further guidance and must wait for additional users to report the problem for it to receive adequate attention. There is certainly no shortage of information, yet no additional details or data have been requested. My feedback was closed without any communication, and while Thomssie did receive some responses, they were neither constructive nor helpful.

Thomssie and I have likely found a fix, though its reliability is still unclear. We both used this SubscriptionStoreView API. SubscriptionStoreView(groupID: "someGroupId", visibleRelationships: .all) However, Thomssie has released a patch that changed the previous API to this SubscriptionStoreView using productIDs. SubscriptionStoreView(productIDs: ["someProductId1", "someProductId2"]) The latest version of the app now uses productIDs instead of groupID. After waiting briefly until the Subscription Storefront became unavailable again, we noticed that the update using productIDs still worked. We tested this on two devices, one had the app installed with the old version before the update, and the other had the app installed after the update. The device with the old version experienced the Storefront loading error, while the new version did not. On the updated device, the products ("Subscriptions") loaded as expected. Could this issue be related to iOS 18 and this new SubscriptionStoreView API? While all users in my case are experiencing the Storefront problem, indicating they are on iOS 17 or higher, I still wanted to rule out a potential API issue related to changes introduced in iOS 18. I hope this sheds some light on the situation, and we will continue investigating to gather more information about the stability and reliability of the new "fix."

And unfortunately, nothing is working anymore again … this time even while my description update is still in the Pending Review state. The whole storefront does not load. This means that temporarily changing the description doesn’t seem to help anymore. As I found out, it’s also region-based. While my german account doesn’t load anything, my austrian account at least loads the annual subscription. This might be because the austrian account currently has the annual plan. It’s just so frustrating…

Okay, this time it definitely took much longer, but the yearly option eventually became available again. Unfortunately, changing the description to fix the storefront issue is usually only a temporary solution. Once the review team approves the description, the storefront stops loading again. Additionally, I can no longer be sure that it works equally well in all regions.

Could this perhaps be a similar, if not the same, issue as described in this post? https://developer.apple.com/forums/thread/759122?page=1#797463022

Hello, Up until yesterday, everything was working perfectly, and I didn’t need to adjust my subscriptions for the storefront to function. Unfortunately, I noticed yesterday that with my German Apple account, only one of the two subscriptions in a subscription group was displayed on the storefront. I have a monthly and a yearly subscription option, but only the monthly one was shown. However, with an Austrian account, both options were displayed normally. This suggests that the issue might be region-specific, and it makes me question the reliability of the information on which countries my subscriptions are available in. I changed the description back and forth, submitted it for review, and within a few minutes, the yearly option reappeared on the storefront. However, today, the entire storefront failed to load again. This time, the entire storefront is down, not just one option. I just edited and resubmitted both subscriptions, but now only the monthly option appears. This problem is unacceptable. It's terrible not being able to rely on the subscription service functioning properly. If this continues, I will be forced to look for alternatives soon.

Hi! I encountered the same issue. In Xcode, my App Store Connect subscriptions loaded perfectly without a StoreKit configuration once everything was set up (and tested) correctly. Everything also worked fine in TestFlight, but in the App Store itself, nothing worked. The subscriptions themselves work; I can redeem codes or manage my subscription, but StoreKit2’s SubscriptionMarketingView doesn’t load the storefront. My subscriptions were approved, and my app was approved—everything seemed perfect. However, the storefront didn’t load, and I couldn’t figure out why. I added the In-App Purchase Intent, hoping it would fix the issue, but it didn’t. What ultimately fixed the issue was editing the subscription description back and forth every time Apple’s review team approved my description. Right after approval, it stops working again until I force another review by changing the description. Please fix this issue as soon as possible.