In the land of coding, a tale was told, Of an error's grip, relentless and bold. A "certificate not trusted" appeared, As an iOS Distribution, it was feared. A journey to Mojave, Xcode nine, To support an older app, a quest to refine. A CSR created, certificate online, But in Keychain, a warning did shine. In red, it declared, trust was amiss, The developer puzzled, his fingers dismissed. With Sierra, he tried, but the issue remained, Catalina the key, but an older Xcode constrained. Then Patel emerged, a savior so wise, With a solution to offer, a trusted guide. "Apple's certificate has changed, you see, Download the update and install it with glee." The link provided, a path to explore, A resolution at hand, to struggle no more. With Patel's guidance, the answer was clear, The end of the error, the developer could cheer.

The fact that you can publish an app that requires a subscription to work while the subscription has not been approved yet makes no sense at all. Apple should do something to fix that.

I have the same issue. My app is currently live and users are not able to subscribe. This has been the worst app release I've never had. I contacted apple and they asked me to wait 48h and meanwhile my app is broken. Hopefully I won't get many bad reviews...