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. Is your Developer Account compliant?
Apple Developer Account
Go to Apple Developer Account β Business tab
Confirm all pending agreements are signed
Verify the Developer Program License Agreement is current
Ensure the $99 USD annual membership is active
Confirm no outstanding issues or account violations
Google Play Console
Confirm the $25 USD registration fee is paid
Go to Settings β Developer Account β Organization Details
Confirm organization verification is completed and status is "Verified"
Check for policy compliance or warnings
2. Have you updated your event content?
π¨ If you're updating the app with new event content, at least one live event must be linked to the app for app store testing.
Launch Screen
Go to Studio β Your App β Branding β Launch Screen
Upload a new launch screen if the event branding has changed
Size: 1125 Γ 2436 px
Format: PNG or JPEG
Margins: 240 px top/bottom (no content in this area)
Background: Plain
Do not remove the "Swapcard test user" profile. It is required for app store review.
3. Have you updated store information?
Google Play Store
Go to Studio β Your App β Store Information β Google Play
Update the Play Store banner if needed (1024 Γ 500 px)
Review and update:
Short Description (80 characters max)
Long Description (4000 characters max)
Use accurate, functional language:
Mention app features (networking, agenda, chat, streaming)
Avoid only talking about the event
Do not use prohibited terms like "Covid," "best," "top," "pandemic"
Apple App Store
Go to Studio β Your App β Store Information β Apple App Store
Review and update:
App Description (4000 characters max)
Keywords (80 characters max)
App Name (30 characters max)
Use clear, descriptive language focused on functionality.
4. Have you verified iOS API Keys?
Go to Studio β Your App β iOS Setup β API Keys
Confirm all iOS keys are valid:
App Store Connect API Key
Push Key ID
Issuer ID matches your Apple Developer account
If keys are outdated:
5. Have you verified final settings?
In Studio
Confirm app details are accurate
Verify the correct events are linked
Check custom domain settings if used
Ensure branding is consistent
For Testing
Review app content for store compliance
Confirm support URL and contact information are correct
Ensure the Swapcard test user profile is present
What are common reasons for app rejection?
Avoid these issues:
Expired Apple Developer membership
Unverified Google organization account
Expired or invalid iOS API keys
Launch screen using outdated branding
Use of prohibited language like "Covid," "top," "best"
Incorrect or missing support info
Submitting without a live event
Deleting the Swapcard test user before publication
What should I include in my store descriptions?
β Do NOT use:
Health-related terms: "Covid," "Corona," "Pandemic"
Superlatives: "Best," "Top," "Premier," "Ultimate"
Unsupported claims: "Most popular," "Award-winning"
β Instead, focus on:
Networking features (attendee connections, profiles)
Agenda and session browsing
Live streaming and content access
Interactive tools (Q&A, polls, chat)
Need Help?
Developer account issues: Contact Apple or Google support
Studio configuration help: Contact your Swapcard account manager
API key setup: Follow this guide
Google Play Service Account: Follow this guide
Once youβve completed the full checklist, your branded app is ready for update submission.
Completing the pre-update checklist ensures your branded app update proceeds without delays or rejections. By verifying developer account status, updating store assets, and keeping API keys and test profiles in place, you streamline the approval process for both Apple and Google.
If youβre ready, submit your update request with confidenceβyour app is set up for success.
Read more