How to Push an Update to Your Whitelabel Mobile App

By Sparkforge Support Team ·Last reviewed May 3, 2026

Generate a new build from Sparkforge, create a fresh version in App Store Connect, attach the build, update metadata, and submit for Apple review.

Once your whitelabel Sparkforge mobile app is live in the App Store, every bug fix, feature, or branding change ships as a new version through App Store Connect. The flow below covers a standard iOS update.

Prerequisites

  • Active Apple Developer account with access to your app record.
  • A new build uploaded via Xcode or Transporter (Sparkforge handles this through Generate Build).
  • Updated metadata if screenshots or descriptions changed.

Step 1: Start a new build

  1. In Sparkforge, click Launch App > Generate Build > Start App Build.
  2. Wait for the on-screen build progress to finish before moving on.

Step 2: Sign in to App Store Connect

  1. Open App Store Connect and sign in with your Apple Developer credentials.
  2. From the Apps Dashboard, pick the app you want to update. The current live version shows in the listing.

Step 3: Create a new version

  1. On the app page, click Add New Version.
  2. Enter the new version number. It must match the build version uploaded from Xcode and follow sequential order (1.0 → 1.1 → 1.2).

Step 4: Update app information

  • What's New in This Version: Note bug fixes or new features.
  • Screenshots and previews: Refresh anything that changed in the UI.
  • Metadata: Adjust description, keywords, or support URLs if needed.

Step 5: Attach the new build

  1. Under Build, click Select a Build Before You Submit.
  2. Choose the build you just generated and save changes.

Step 6: Review privacy and compliance

  • Confirm your Privacy Policy URL is current.
  • Revisit the App Privacy questionnaire if data collection changed.

Step 7: Submit for review

  1. Double-check icon, screenshots, and metadata.
  2. Click Submit for Review. Apple's team will test the update before publishing.

Common update errors

  • Build not visible: Confirm the build uploaded via Xcode or Transporter with the correct version number.
  • Version mismatch: The version in App Store Connect must match the Xcode value.
  • App rejected: Read Apple's rejection reason, fix it, and resubmit.

Frequently Asked Questions

How long does Apple's review take for an update?
Most reviews complete within 24-48 hours, but Apple does not guarantee a timeline. Submit early if your release date is fixed.
Do I need to bump the version number for every update?
Yes. App Store Connect rejects duplicate version numbers. Increment sequentially (for example 1.4 to 1.5).
Can I roll back a published update?
Apple does not offer a rollback button. To recover, ship a new build with the previous code as a higher version.
What if my build never appears in App Store Connect?
Check that the build uploaded successfully via Xcode or Transporter and that the version string matches what you entered in App Store Connect.

Was this article helpful?

Related Articles