Same here. App got rejected because loading spinner was taking too long. Everything works fine when I test via TestFlight on my device. However app still got rejected. The App Store review team sent me a screenshot of the loading spinner on the paywall page. This is very frustrating and outside of my control. What do I even do? :(

Hi all,

Thanks for flagging this. We understand how frustrating this is, especially with App Review rejections involved.

We’ve recently uncovered what appears to be a bug in StoreKit 2 that’s affecting various environments (including but not limited to iOS 18.4) and seems to occur intermittently rather than consistently. Specifically:

• in the iOS 18.4 simulator, there are confirmed issues with loading products - this is where we’ve seen the most consistent issues so far.

• in Sandbox, TestFlight, and App Review environments, we've seen delays both in loading products and in presenting the payment sheet after a purchase is initiated in different environments

• these issues have not been observed in production so far.

We’ve filed Feedback with Apple and are actively tracking this on our side (see GitHub issue #4954 for updates and context).

At the moment, we’re not aware of any reliable workaround, since these issues stem from StoreKit itself, there's unfortunately not much that can be done from the app or SDK side. 

We’re keeping a close eye on the situation and will share any updates or potential workarounds as soon as we have them.

Best,
Gui

My app was rejected again due to this issue… but I also can’t reproduce it in my side...

Hey all,

Just wanted to share a quick update here for visibility: as you may have seen on GitHub issue #4954, Apple has responded to our Feedback submission and confirmed they believe they’ve identified the root cause behind products failing to load.

They also mentioned that a potential fix is coming in an upcoming release.

Separately, in that same GitHub thread, there’s been some useful discussion around app review rejections, including a solid explanation from Andy (on our Core SDK team) about what might be triggering these and how to think about them.

If you’re running into this issue, it’s worth reviewing the thread and trying some of the workarounds or mitigations mentioned, especially ahead of submission, as review behavior can be inconsistent and tricky to debug.

Best,

Gui