What should I check before submitting an app update?
Before requesting an update, confirm all store, account, and content requirements are met to avoid delays or rejections.
1. Developer Accounts & Access
Make sure both your Apple and Google Developer accounts are ready:
You have organizational developer accounts (not personal).
All agreements and memberships are active and up to date.
You’ve invited ios@swapcard.com and android@swapcard.com with the correct permissions.
🔗 See: Apple Account Setup and Requirements for iOS
🔗 See: Google Account Setup and Requirements for Android
2. Required Assets & Branding
Prepare all visual and written assets in advance to speed up your setup:
App icon (1024×1024 px)
Launch screen image (1125×2436 px, PNG/JPEG, no transparency)
Home logo (SVG or PNG, white background, no gradients)
Google Play banner (1024×500 px)
App name, short and long descriptions, and keywords
Colors and fonts that match your event or brand guidelines
🔗 See: Graphic and Content Requirements for Branded Apps
3. Technical Setup
Ensure all credentials are created and accessible before submission:
Apple: API key, issuer ID, push key ID, and related files are ready.
Google: Service account key (JSON file) is created and stored safely.
🔗 See: Apple Account Setup and Requirements for iOS
🔗 See: Google Account Setup and Requirements for Android
4. Studio Preparation
When setting up your app in Studio:
Confirm your entity name and team ID match your Apple Developer account.
Link the correct event(s) to your branded app.
⚠️ Do not delete the Swapcard test user. It’s automatically added for store validation and is invisible to attendees in the event or community.
5. Final Checks Before Submission
Before submitting:
Verify all API keys and credentials are valid.
Review your branding, descriptions, and screenshots.
Make sure all store requirements are met and your content follows naming guidelines.