Thank you very much for your help!

I am using this code to fetch my saved events. They are then used as options for my widget configuration. Is there a better way to do this?

Thank you. The problem is in my WidgetConfigurationIntent @MainActor private func fetchEvents() -> [Event] { guard let modelContainer = try? ModelContainer(for: Event.self) else { return [] } let descriptor = FetchDescriptor<Event>(sortBy: [SortDescriptor(\.dateCreated, order: .reverse)]) guard let events = try? modelContainer.mainContext.fetch(descriptor) else { return [] } return events } Is there a way how I can fix this?

This is a great idea. Thank you so much! I will continue to share all my findings with everyone in our existing forum. And I kindly ask others to share their findings too.

Hey. The feedback assistant case resolution is now "Investigation complete - Unable to diagnose with current information" so I am not sure if Apple can do anything with it. The work-around has been working for me. I hard-coded the product ids from the AppStoreConnect - Subscriptions. The store hasn't become unavailable on the new version. It is working perfectly. Another developer tried it and it is working for him too. Please can you keep me informed about new responses from Developer Support?

Hello. My friend and I might have found a fix. But further testing is required. Instead of using SubscriptionStoreView(groupID: "someGroupId"), try using SubscriptionStoreView(productIDs: ["someProductId1", "someProductId2"]). We tested it on my app on 2 devices: the old version shows "Unavailable", but the new update works. Check SPEEDCUP's latest answer in this post for more info. Could you try using productIDs instead of groupID in your app and let me know if it solves the problem? Thank you!

Hello. My friend and I might have found a fix. But further testing is required. Instead of using SubscriptionStoreView(groupID: "someGroupId"), try using SubscriptionStoreView(productIDs: ["someProductId1", "someProductId2"]). We tested it on my app on 2 devices: the old version shows "Unavailable", but the new update works. Check SPEEDCUP's latest answer in this post for more info. Could you try using productIDs instead of groupID in your app and let me know if it solves the problem? Thank you!

Hello. My friend and I might have found a fix. But further testing is required. Instead of using SubscriptionStoreView(groupID: "someGroupId"), try using SubscriptionStoreView(productIDs: ["someProductId1", "someProductId2"]). We tested it on my app on 2 devices: the old version shows "Unavailable", but the new update works. Check SPEEDCUP's latest answer in this post for more info. Could you try using productIDs instead of groupID in your app and let me know if it solves the problem? Thank you!

Hello. My friend and I might have found a fix. But further testing is required. Instead of using SubscriptionStoreView(groupID: "someGroupId"), try using SubscriptionStoreView(productIDs: ["someProductId1", "someProductId2"]). We tested it on my app on 2 devices: the old version shows "Unavailable", but the new update works. Check SPEEDCUP's latest answer in this post for more info. Could you try using productIDs instead of groupID in your app and let me know if it solves the problem? Thank you!

Hi. Unfortunately, I haven't been able to find any fixes. Currently my subscription store is in the "Unavailable" state more than actually being available to the users and it has been 3 weeks since the subscription was released. Also my descriptions haven't even been approved again and the store is "Unavailable" anyways. So there is actually nothing I can do anymore. My users are unable to subscribe or even see the pricing options. It is really frustrating and causes a huge headache for me.

I have the exact same problem. The subscriptions worked properly for a week, but now they are becoming unavailable again. I have to resubmit the description every day just so my users can see the subscriptions.

Could be also another problem. But my app and subscriptions are available to all countries and regions and still experiencing this problem.

Thank you for the fast reply. Here is my FB# ticket number: FB14251069