Rubber Duck
Catch App Store rejection issues before Apple does.
455 followers
Catch App Store rejection issues before Apple does.
455 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.
Very useful tool 👍🏻 How do you match your tests with App Store validations?
Macky
So you still need humans at background this is not fully automated right ?
Macky
@tony_yan_1111 Yess Tony that's right, it is not fully automated and NEVER will be. The goal is to check the app like how Apple checks.
Makers Page
Oof, this would’ve saved me a week last spring. Got dinged for a missing privacy string and a weird crash only on iPhone SE. Like the human-on-real-device bit. How deep do your automated checks go? e.g., Info.plist sanity + broken onboarding paths?
Macky
@alexcloudstar Hey Alex! Yes the automated checks goes 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
After this a human QA manually checks all the paths and content to make sure it fits the Apple rules. Let me know if you have any other questions!
Macky
@aseemwangoo I can’t ready your code. You are just submitting the compiled app. Hope that makes it clear.
This is clever — catching App Store rejections before submission saves so much time.
What are the most common rejection reasons it catches?
Also, does it check for the vague "Guideline 4.3" spam filter stuff?
Nice work 👏
Macky
@nefayran Thanks Rodion, really appreciate it! The issues RubberDuck catches most often are the really frustrating, preventable ones: missing required elements like a restore purchases button or privacy link, broken or incomplete flows, layout problems on certain devices, crashes, and metadata inconsistencies inside the IPA. These are the things Apple flags all the time and usually cost you an entire week. As for Guideline 4.3, that one is mostly subjective on Apple’s side, but we do look for the common patterns that typically trigger it, like template-style or incomplete apps. We can’t compare your app to Apple’s internal database, but we can definitely catch the obvious things that reviewers tend to see as “spammy” or low-quality.
AidaJet
Congrats on the launch! The hybrid approach of automation + human testers is super smart. How fast is the typical turnaround time for a full Duck Report after uploading an IPA?
Macky
@piyush_kumar_thakur Hey Piyush! It is about 4 hours but usually faster than that.
AidaJet
@sayuj_suresh That's an awesome turnaround time and a great advantage for individuals or small teams. Wish you and Rubber Duck the best.
Really thoughtful solution. Pre-review issues like metadata gaps, edge-case crashes, and device-specific bugs cost teams real time. Rubber Duck fills a painful gap in the pipeline. Congrats on the launch!