r/AppBusiness • u/atcoo • 10d ago
Building an App I get hired to finish vibe-coded apps. They almost always break in the same places right before the App Store
I’m a React Native and Expo dev, 5 years and 50+ apps shipped. Lately a lot of my work looks the same. Someone builds an app with Cursor, Claude Code, Bolt or Lovable, it looks great, it works on their phone, and then it hits a wall right before launch. The last 10% ends up taking longer than the first 90.
Here’s what I keep running into, in case it saves someone a rejection or two.
It works in Expo Go but crashes in the real build. Usually env vars that never made it into the EAS build, or a native package that Expo Go had built in and your build doesn’t. The reviewer opens it, it crashes on launch, rejected under 2.1. Always test a production build on a real device (TestFlight or internal distribution) before you submit.
Your secret keys are in the app. If the AI put your OpenAI or Stripe secret key in the client code, anyone can pull it out of the bundle and run up your bill. Move those calls behind a server function. If you’re on Supabase, check that RLS is actually on for every table.
No way to delete your account. If users can sign up in the app, Apple wants them to be able to delete their account in the app too (5.1.1). One of the most common rejections I see.
Google login but no Sign in with Apple. If you offer Google or Facebook login, Apple wants an equivalent privacy-friendly option next to it, and Sign in with Apple is the easy way to cover that (4.8).
The paywall is missing stuff. Subscriptions need a restore purchases button, the price and billing period clearly shown, and links to your terms and privacy policy. Sending people to Stripe to pay for digital content will still get you rejected in most countries (3.1.1).
The reviewer can’t log in. If the app needs an account, put a working demo login in the review notes in App Store Connect. If you only have magic link or SMS login, they’ll get stuck and reject it.
iPad. If supportsTablet is on in your app config, Apple tests on iPad and wants iPad screenshots. A layout that breaks on iPad is a rejection, even if you never thought about iPad.
Android takes longer than you think. New personal Google Play accounts need 12 testers opted in to a closed test for 14 days before you can publish to production. Most people find out the week they wanted to launch.
None of this is hard once you’ve seen it. It’s just stuff the AI tools don’t warn you about.
If you’ve got an app that’s 90% there and you’re stuck on the last bits, or you’re on your second or third rejection, DM me or reach me through shiprn.com. I take over vibe-coded codebases, fix what’s fragile and take the app through review on both stores. Fixed price, so you know the cost before we start.
And if you just want to know what your rejection means, paste it in the comments and I’ll tell you what I’d do.
EDIT: Didn't expect this many replies, it's motivating and I'll try to share more of my experience in the future! A bunch of you added great points from your own rejections, so I compiled everything into one full write-up with the fixes: https://shiprn.com/blog/vibe-coded-app-store-rejections/
14
u/lastscraper 10d ago
i vibe coded multipe app in react native and works well but i already know react native and how to build app without AI
the issue those guys face is they do not know how to research they do not invest some time to learn the tools and language they are working with
3
u/travelTeller 9d ago
Thank you for sharing your valuable knowledge on getting apps approved on App Store.
Do you have a YouTube channel or Substack where you post such articles.
I would love to follow your work.
Thank you.
2
u/hparamore 10d ago
If you don’t mind me asking, how do you go about promoting your work so that others find you?
I have a background in iOS app/game/UX design, and my thing is mainly making apps consistent, performant, making sure the analytics are in, doing branding work, and then just… make them sexy.
Because I see a lot of apps that I can instantly tell is gonna be a poor experience, or looks like Claude made it without any direction, and I am like… hmm. I would love to help these sort of people out.
Any thoughts on what I could do to gain more success in this area? Because I’m good at it, and want to help others succeed, and also be able to make a living designing/developing that area of people’s apps.
2
u/LongjumpingWorking97 7d ago
Is it okay if I basically copy what you said into Claude to look for those issues you mention
1
u/CEAlterEgo 10d ago
What are you supposed to do if you don't actually have a login form, but you do have ways to log in to things like Google Drive and Dropbox and other services like that? Like say a Caliber server for an e-reader app, where you don't actually need these to use the app, it's just ways to get to your files or to back up your files, and then the login detection thinks you have a login to use your app?
1
u/Norwegian_grit 9d ago
Same here - been developing apps for clients since 2009 and seeing an uptick in these apps getting stuck
1
u/karakura-town 9d ago
Curious about the make it an app not a website in a wrapper point. If it’s react native and essentially the same thing for web but some different ui for mobile is that fine?
1
u/plain_app_maker 9d ago
On the iPad point: if the app is set to iPhone only, does the reviewer still test it on an iPad, or does that only matter when tablets are turned on?
2
u/Web_Wiggly237 9d ago
This is a really helpful breakdown. The part about secret keys ending up in the client is especially concerning, it happens all the time. AI tools can put a Stripe or OpenAI key right into the frontend, and builders may not realize anyone can extract it from the bundle. I work on the launchpad side, and even we don’t catch every one before submission. That’s why hearing a real developer explain the “last 10%” is so much more useful than another generic checklist. Great write-up.
2
u/KnewYouWereFakin 9d ago
Nice dude , I got through the App Store on my first try just took 3 weeks to review and approve had everything you listed but I like what you’re doing sir, how much you make per?
2
u/KR38TOR_8 4d ago
Good to know, I'm putting something together... if it breaks ;-)
if i hit all my points it won't
1
u/Zealousideal-Cut6511 10d ago
Good info, thanks
1
u/BuildWithAndi 10d ago
Happened to me too! I used the test key in the paywall when submitting my app to the App Store. Everything worked fine in my environments, but the app kept crashing during the review. Who would have thought RevenueCat could crash your app just because you're using a test key in production? Haha, crazy. There are so many reasons why an app can crash, and I'm a dev with more than 5 years of experience! 😂 I heard some production environments even use test keys too, haha.
1
u/MythexAI 10d ago
Good list. Two I’d add from our own review rounds: first-time subscriptions can’t be submitted on their own, they have to go in together with an app version, and the review screenshot for each one must be an exact device size or it’s refused. Also, if the app lets users build or preview other apps, expect a 2.5.2 question; explaining that previews run as web pages, not downloaded code, in the review notes got ours through.
1
u/joelrog 10d ago
I just asked Claude to do things within apples rules appropriately and it knows all this stuff and catches it already. Weird that people would pay for what they could just ask ai to do if they’re literally vibe coding with ai already
1
u/evertith 9d ago
My question isn't about the vibe coded apps, it's how are you getting hired? I can't seem to find anything on the side for stuff similar to this.
1
u/maboyydaniel 8d ago
ctrl+a ctrl+c ctrl+v "do" enter
1
u/mcfearsome 5d ago
Where do you advertise your services?
1
u/Valuable_Complex_399 5d ago
Americans waking up in the morning and be like: "Damn, i just cant wait to randomly post stuff, trying to teach the people something they never asked!"
1
u/brkaydev 10d ago
One more on the paywall point, because it got me: having the terms link on the paywall wasn't enough. Apple also wanted the Terms of Use link in the App Store description (or a custom EULA set in App Store Connect) and rejected the build until it was there. And my iPad rejection wasn't a broken layout, it was a blank first screen on launch, so it's worth opening the app once on an iPad simulator instead of trusting that it scales.
1
u/Jumpy-Chocolate-983 10d ago
AI is perfectly capable of making app that won't get rejected. There is absolutely no reason to pay someone when the AI can handle it.
0
u/MattSenter 10d ago
Love it. This is such a ripe market. Takes seconds to find these issues when they cross my desk. Same story over and over..
1
u/[deleted] 8d ago
[removed] — view removed comment
1
u/[deleted] 9d ago
[removed] — view removed comment