Rubber Duck
Catch App Store rejection issues before Apple does.
458 followers
Catch App Store rejection issues before Apple does.
458 followers
Rubber Duck scans your iOS app before you submit it to the App Store. We combine automated checks with human testers on real devices to catch the issues Apple flags the most: crashes, incomplete build flows, missing privacy data, inconsistent metadata, broken onboarding, and more. Upload your IPA → we test → you get a clear actionable Duck Report.
Hi everyone! I'm the maker of Rubber Duck. After shipping iOS apps, I realized how unpredictable App Store review can be. Even great apps get rejected for:
Missing metadata
Small UI issues
Broken flows on certain iPhone models
Forgotten privacy entries
One-off crashes Apple found
Each rejection set the launch back days. So I built Rubber Duck to be the “review before the review.” It combines automated checks with human testers using real iPhones like an App Store reviewer, but faster and kinder.
Excited to hear what you think and how we can make this even more useful!
@sayuj_suresh This is such a smart gap to solve, so many teams only discover App Store issues after a rejected submission. Having a pre-submission “duck check” that blends automated scans with real human testers feels like the kind of tool every iOS dev wishes existed sooner.
How deep do your automated checks go? Are you able to flag things like missing privacy manifests or issues with entitlement usage before Apple does?
@fernando_scharnick Hey Fernando! Ikr! This is at least a decade old problem and I thought someone would have it built but sadly nooo :( How does the automated checks go? Right now Rubber Duck’s automated checks go through the IPA itself so we scan things like:
Info.plist
required keys & capabilities
icons / assets
entitlements
permissions
basic binary issues
missing or invalid metadata inside the build
device compatibility checks
We do not currently scan what you enter in App Store Connect’s privacy questionnaire because that data lives in your dev account. But our human QA pass often catches areas where the privacy info should be updated e.g. if the app uses camera/mic/location but Info.plist or flows don’t match what Apple expects.
Let me know if you have any other questions!
@vouchy Yo Van, also, incredible name.
For me, the breaking point was a string of rejections where I kept losing entire weeks over tiny, preventable issues. After a few successful releases I started to understand what Apple actually expects… but before that, it was just this painful cycle of: Submit → wait days → get rejected → fix one tiny thing → wait again.
Developers shouldn’t have to waste a week because of something a pre-check could’ve caught in minutes.
Swytchcode
Kudos to your efforts! Are you bringing in something for the play store?
@chilarai Hey Chilarai! Thank you. Google is pretty lenient on their approval, so I don't think we need it. I will maybe add just plain QA testing in future for play store.
Triforce Todos
Huge congrats on shipping! I can already see this becoming essential for small teams launching apps.
@abod_rehman yesss!
@aseemwangoo I can’t ready your code. You are just submitting the compiled app. Hope that makes it clear.
HushLink
Awesome work!! Will be using soon.
@danielkazak Thanks Daniel! Just email me at founder@tryrubberduck.com when you are ready. I will personally help you review!