Skip to main content
Question

Vanilla iOS App getting Error #23

  • May 6, 2026
  • 3 replies
  • 44 views

Forum|alt.badge.img

I went through the whole Troubleshooting checklist. I haven’t even submitted a new release since December, so nothing has changed. I have only one Offering, one Entitlement, and 3 Products, 2 of which I’m using. It’s a SwiftUI app in XCode. It’s as simple a configuration as possible. And it started randomly giving me Error #23 recently. 

The only thing I can think of is that my Apple Dev Subscription did renew during that period. But all the numbers stayed the same. I even re-generated the API and In-App keys in the store. I've tried updating all the client libraries and running it from XCode as well. Nothing gets rid of the error. Any ideas?

3 replies

matt-heaney
RevenueCat Staff
Forum|alt.badge.img+4
  • RevenueCat Staff
  • May 7, 2026

Hey ​@samkass!

Thanks for the question. I’m Matt from RevenueCat, and I’d love to help with this.

To confirm, is your app currently live?

The most common reason this starts happening with a live app is that there is a new agreement that needs to be accepted in App Store Connect. If there is, this can cause this error to appear.

You can check this in the Business section of App Store Connect. If there is an agreement waiting to be signed, accepting it should help resolve the issue. Please note that it can take a short amount of time for the change to take effect after the agreement has been accepted.

If this is not the case, and your developer account is still active, please let me know and I’ll dig deeper to get this resolved. I wasn’t able to find a RevenueCat account linked to your account, so if this does not resolve the issue, could you please private message me your app ID? I’ll then be able to investigate further.

I hope this helps!


Forum|alt.badge.img
  • Author
  • New Member
  • May 7, 2026

It was indeed the additional agreement. But usually Apple shows these in a banner when you log in, or alerts you in the Business section directly. This one I had to drill down to my legal entity and scroll down to see that an additional addendum was still pending. I wish Apple gave a more prominent alert, or gave some way for RevenueCat to get better diagnostic information as to why the calls are failing. Anyway, solved, thanks.


matt-heaney
RevenueCat Staff
Forum|alt.badge.img+4
  • RevenueCat Staff
  • May 11, 2026

Hey ​@samkass ,

Thank you for the update! I’m so happy to hear that the issue is now fully resolved for you!

I’m sorry to hear the banner wasn’t displayed in App Store Connect. Being able to track these sorts of issues is something we’re very keen on improving, and I agree, it would be ideal to display a warning in the RevenueCat dashboard to highlight these required changes before they become an issue. However, we’re unable to get this information from App Store Connect. We have discussed a few potential routes to work around this, but none would be fully reliable without that data. It’s an area we hope to improve in the future if we’re able to.

I’m sorry again that you ran into this issue.

If there is anything else I can do to help, please let me know. We’re always happy to help!

Thanks!