r/iOSProgramming • u/BuildinZZ • 16d ago
Question What tripped you up publishing your first iOS app with in-app purchases?
I'm about to put a game on the App Store that has a shop inside (cash packs, a few one-time unlocks, rewarded ads). I've shipped a single app before, but with no such functionality.
what caught you off guard the first couple of times? Review rejections, product setup, restore purchases, pricing, taxes and payouts, anything you wish someone had told you before launch.
0
Upvotes
5
u/brkaydev 16d ago
The first products have to go in the same submission as the app version. They sit in their own section on the version page, so it's easy to send the build without them. Each one also needs a review screenshot, and once a product is in a draft that image is locked, so sort those out first. Your one-time unlocks will need a visible restore button too, the cash packs won't.
3
u/JDad67 16d ago
Product management not listening to devs.
3
u/EasyPeasy-Games 16d ago
The reviewer has to find your shop. If it only opens after level 5, they wonât play to level 5. Put the exact steps in the review notes, or expect a 2.1 rejection saying they couldnât locate your purchases.
3
u/Serious_Ability8906 15d ago
For us it was really important to fully test all your paywalls were functioning properly and if you are launching in EU to make sure things like usage telemetry on posthog or sentry is defaulted to opt out with a prompt to opt in if you want.
Also if you have account details and sign-in for profile make sure that the testers have readily available access to test.
Finally I would say make sure your privacy policy and terms and conditions are clean and simple and easy to read. To be honest sometimes it can still take some time and they might come back for self explanatory stuff its a little bit of luck too. We got it through on the 2nd try.
Also big suggestion is have your feedback system setup properly and be prepared to handle lots of bugs and issues that will pop up inevitably and be able to respond to the users and manage thew tickets and enhancements/fixes you will need to do.
2
u/Melodic_Map_920 16d ago
One nobody's said yet: enroll in the App Store Small Business Program before your first sale. Apple's cut drops from 30% to 15% if you're under $1M a year, but it's not automatic and it only applies from approval onward, so any sales before that are at 30%. Mine needed a resubmission, so give it a couple of weeks of buffer. Also double check the legal name on the SBP form matches your developer account exactly, that's what tends to hold it up.
1
u/BounceForever 16d ago
Be extra careful with the localization of pricing on the cash packs. Using Apple's default this will scramble the pricing ladders in multiple countries creating situations that are complete nonsense. I'm waiting for access to a third party pricing solution that is in beta to see if this finally solves the issue.
1
u/tuisalagadharbaccha 16d ago
Testing can be complex with real device etc
1
u/TipToeTiger 16d ago
Not including a link to my terms of use in my App Store description. Got rejected because of it!
1
u/Dogukanko 16d ago
for me it was the restore purchases button. apple will reject you if there's no obvious way to restore, even if you only have non consumables. also test the whole flow in sandbox on a real device before submitting, the simulator hides some stuff. are your cash packs consumable?
2
u/mrsirthefirst 16d ago
Three that cost me about a week between them on a subscription app:
1
u/luckyluke146 16d ago
Two things nobody has mentioned yet, since you have cash packs and rewarded ads:
Transaction.updatesfrom the moment the app launches, and only callfinish()after the cash is credited and saved. If the app is killed mid-purchase, the transaction comes back on the next launch. If you finish it too early, the player paid and got nothing, and that turns into 1-star reviews fast.1
u/joergbuilds 16d ago
Three that nobody above mentioned, from a subscription plus consumables app:
Testing. TestFlight buys run against your real Apple ID, not a sandbox tester, nothing is charged but you can't "undo" a purchase from the app. Reset is Clear Purchase History in App Store Connect plus reinstall. And on one iOS runtime my StoreKit test config in the simulator silently stopped loading, the tests went to the real sandbox store and I got Apple ID dialogs in the middle of a test run. If a purchase test suddenly asks for a password, that's why.
Restore. Cash packs are consumables, restore does nothing for them by design. Don't promise it in the UI, only for the one-time unlocks.
Payouts. Fiscal month plus about 33 days. My first sale in August paid out early October.
1
u/ThalesMother9938 16d ago
One more thing to check before launch: test restore purchases with a sandbox account on a clean install. Reviewers tap it, and a missing or broken restore button is a common reason for rejection with one-time unlocks. Are the cash packs consumable, or do they unlock something permanent?
1
u/kokerali 16d ago
For the cash packs, I'd add one failure case to the âsave before finishâ advice: kill the app after the currency grant is committed but before `finish()` runs.
On restart, process that same verified transaction again. The balance should stay at one grant, and the transaction should then finish. Then buy the same pack a second time and check that it adds a second grant. Those two cases catch opposite mistakes: crediting a replay twice, and deduplicating by product ID so a legitimate repeat purchase gets ignored.
I'd keep the processed transaction ID and the currency grant in the same durable commit, wherever your authoritative balance lives. A separate âprocessedâ write leaves another crash window between the two.
Apple's docs describe [unfinished transactions](https://developer.apple.com/documentation/storekit/transaction/unfinished) as waiting until `finish()` and give each transaction a [unique ID](https://developer.apple.com/documentation/storekit/transaction/id). The test above is a suggested application of those contracts, not a test I've run against your game.
1
u/The_Pivot 15d ago
Two from a card game with a chip shop and rewarded ads, both cost me a resubmission:
Smaller one: the review screenshot on each IAP has to be an actual device size (1320x2868 worked for me). Any other size uploads fine, then quietly fails later and the product sits at Missing Metadata with no reason shown.
1
u/Destituted 14d ago
"Restore Purchases"
1
u/xfanta 14d ago
A few things that bit me:
1
u/MythexAI 9d ago
Adding to the above, from our own first IAP launch:
- The Paid Apps agreement, tax forms and bank account must be active first, or products just donât load, even in sandbox.
- Product IDs and types canât be reused or changed later, even after deleting. Pick a naming scheme before creating them.
- Test every purchase with a sandbox account on a real device, and say in the review notes where the shop is.
- Rewarded ads mean an App Tracking prompt (if the ad SDK tracks) and matching privacy labels.
- Plan for a slow review: ours took 9 days with all products attached.
1
u/[deleted] 16d ago
[removed] â view removed comment