App Store Submission
From uploading your Xcode archive through App Privacy labels to submitting for review, step by step.
The full path to publishing your iOS app on App Store Connect. We assume you've completed Before You Publish and iOS Setup.
iOS build/archive requires a macOS + Xcode environment. The App Store Connect UI changes often, but the flow (upload archive → app info → privacy labels → submit for review) stays the same.
1. Archive & upload
- Following iOS Setup, set
PRODUCT_BUNDLE_IDENTIFIERandDEVELOPMENT_TEAMinproject.ymlto your own values and runxcodegen generate - In Xcode, select a real-device target → Product → Archive
- Organizer window → Distribute App → App Store Connect → Upload
- Wait for the uploaded build to appear in App Store Connect (a few minutes to tens of minutes of processing)
The SDK's xcframework includes dSYMs, so Validate App raises no symbol-related warnings — no extra action needed.
2. Create the app record in App Store Connect
- App Store Connect → Apps → New App
- Enter platform (iOS), name, primary language, Bundle ID (the value you set above), and SKU
- Create
3. App info & listing
- App Information: category, content rights
- Pricing and Availability: free/paid, regions
- Version information: promotional text, description, keywords, support URL
- Screenshots: upload the required per-device-size sets (real app screens)
- App icon: 1024×1024 (included in the build)
4. App Privacy labels
Declare data collection under App → App Privacy.
- Choose types based on what your web app collects (the Unveily SDK itself does no analytics/tracking)
- Indicate whether each data type is used for Tracking
- How to fill: Privacy & Data Safety
Write the Info.plist usage-description strings (e.g. NSCameraUsageDescription, NSFaceIDUsageDescription) truthfully and clearly for the features you use. Unclear purposes or usage strings for permissions you don't use can get you rejected → Production Checklist.
5. Review information & submit
- In the Build section, select the build you uploaded in step 1
- App Review Information: provide a reviewer test account (if login is required) and contact
- Attach the WebView behavior explanation to the review notes → App Review Tips
- For in-app purchases (Pro), submit the StoreKit products alongside review → In-App Purchase setup
- Add to Review → Submit
Apple's review usually takes a day to a few days; on approval it publishes per your chosen release option (manual/automatic).
After publishing
- Web content (HTML/CSS/JS) can be updated freely without re-review
- Changing SDK configuration (feature scope) requires an update submission with a new build (re-review)
- Always increment the build number for the next version
Common sticking points
| Symptom | Cause / fix |
|---|---|
| Build doesn't appear in App Store Connect | Processing delay or Bundle ID mismatch — check Xcode upload logs |
| Can't submit due to missing privacy labels | The App Privacy section must be completed |
| Rejected for unclear permission purpose | Write Info.plist purpose strings truthfully for the features used |
| Rejected as "just wraps a website" | State your native feature usage in the review notes → App Review Tips |