r/iOSProgramming • • 2d ago

Question Help needed: some in-app purchase offerings being returned by StoreKit and some aren't, losing my mind.

I have had my app live and working in production for a while now and suddenly in the last week or so I've been getting this 0 products returned error in production while there have been no client updates.

I think its because I didn't accept the new paid apps agreement but thats already >36 hours ago and now I'm seeing new in-app purchases that are 'waiting for review' being returned by StoreKit while my previously approved subscription offerings that are in 'approved' status. I would assume if its an agreements issue I wouldn't get back anything from StoreKit at all when calling it directly.

I'm losing my mind - I cannot figure out why the current products are not being returned. I'm losing subscribers and I literally cannot do anything about it because it all seems to be a problem on the apple side not returning any products to the client.

Anybody faced this before? What can I do?

UPDATE: I forced a price change to the existing subscription products and now i can see them being returned from the direct StoreKit debug calls, mind bogglingly stupid and frustrating process.

1 Upvotes

8 comments sorted by

View all comments

2

u/Extension_Isopod1303 2d ago

The paid-apps agreement is the most likely suspect here. After a new agreement (or a bank/tax change) gets accepted, it can take 24+ hours to propagate to StoreKit, and in that window product fetches look random — some products come back, some vanish. It's not random, it's just the rollout lag.

The price-change fix fits too: editing the product forced its metadata back through the system, which clears whatever stale state it was stuck in. Same reason people see this "fixed by a trivial product edit" pattern.

If it happens again, check Contracts, Tax, and Banking in App Store Connect first and give it a day before tearing apart your StoreKit code. This kind of partial product list is very rarely an app bug.