Congratulations on building your app! You're ready to submit to the App Store, but you're worried about rejection. That's where Rubber Duck comes in. This guide will walk you through your first scan.
1. Preparing your .ipa file
To scan your app, you need to upload a compiled binary (.ipa file). This is the same file you would upload to App Store Connect. Ensure you build your app for "Generic iOS Device" or a specific real device target, not a simulator, to get a valid archive.
2. Understanding the Scan Process
Once uploaded, our system performs a series of automated checks. We look for private API usage, missing plist keys, and common crash vectors. After the automated pass, a human QA expert reviews your app on a real device to check for UX/UI guideline violations (like Human Interface Guidelines issues) that bots often miss.
3. Reading your Duck Report
Within 4 hours, you'll receive a "Duck Report". This report categorizes issues by severity:
- Critical: Will almost certainly cause rejection (e.g., crashes, major guideline violations).
- Warning: Likely to cause rejection or delay (e.g., missing metadata, minor UI issues).
- Info: Suggestions for improvement but not strictly rejection grounds.
4. Prioritizing Fixes
Start with the Critical issues. These are the showstoppers. Common examples include app crashes on launch (Guideline 2.1) or broken In-App Purchase flows (Guideline 3.1.1). Once those are resolved, move to the Warnings.
5. Re-scanning
After applying fixes, generate a new .ipa and run another scan. Our system will compare the new build against the previous report to verify that the issues have been resolved.