Home/HighLevel/Features/Mobile & Desktop App/How HighLevel lets you push an iOS app update

Mobile and Desktop Apps

How HighLevel lets you push an iOS app update

In short

Updating a white label iOS app with HighLevel involves creating a new build, logging into App Store Connect, adding a new version, editing any changed app details, attaching the uploaded build, confirming privacy settings, and finally submitting the version for Apple’s review.

AreaMobile & Desktop App · Whitelabel Mobile App
Used forDental practice, Real estate brokerage, Fitness studio chain
Setup steps18 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Product agencies that distribute branded client apps can refresh UI assets without rebuilding the whole package.
  • Consultants managing multiple client portals benefit from a single process to roll out bug fixes across all white label installations.

02Whitelabel mobile app updates, explained

The update workflow begins in HighLevel where you generate a new build. After the build completes, you log into Apple’s App Store Connect, create a new version, optionally edit release notes, screenshots, and other metadata, attach the uploaded binary, verify privacy information, and submit the version for Apple’s review.

03How businesses use whitelabel mobile app updates

  • Dental practice. The practice can upload a new build that includes an updated patient intake form. After uploading, they modify the “What’s New” text to note the new form and replace screenshots showing the revised flow. Finally, they submit the version for Apple’s approval.
  • Real estate brokerage. When the brokerage rebrands its client facing app, it generates a fresh binary in HighLevel, updates the logo and marketplace screenshots in App Store Connect, and adds the new version number. The updated app is then sent to Apple for review.
  • Fitness studio chain. The studio adds a new class booking feature to its white label app. It creates a new build, updates the “What’s New” field to describe the added feature, refreshes the preview images, and submits the revised version through the Apple portal.

04The numbers and rules that matter

  • Version numbers must be sequential (e.g., 1.0 > 1.1 > 1.2).

05Before you start

  • You must have access to an Apple Developer Account.
  • A new app binary must be uploaded via Xcode or Transporter.
  • Any revised screenshots, description or other metadata should be ready.

06How to set up and use whitelabel mobile app updates in HighLevel

Update live iOS white label app

  1. In HighLevel, select Launch App, then choose Generate Build and click Start App build.
  2. Wait until the build progress indicator shows completion.
  3. Open a web browser and go to App Store Connect.
  4. Sign in using your Apple Developer credentials.
  5. From the Apps Dashboard, click the app you intend to update.
  6. Inside the app page, press the Add New Version button.
  7. Enter the new version number that matches the uploaded binary.
  8. Ensure the version number is sequential (for example, 1.0 > 1.1).
  9. Provide a brief description of what’s new in this version.
  10. Replace screenshots or preview videos if the user interface has changed.
  11. Edit the description, keywords, or support URLs if required.
  12. In the Build section, click Select a Build before you submit.
  13. Choose the newly uploaded binary from the list.
  14. Save the changes you made to the version.
  15. Confirm that the Privacy Policy URL is correct.
  16. Answer any new questions in the App Privacy questionnaire.
  17. Verify all fields such as icon, screenshots, and metadata are accurate.
  18. Click Submit for Review to send the update to Apple.

07Settings that matter

  • Version number. Determines the sequential identifier for the app update; it must follow the previous version and match the binary’s version.
  • What’s New in This Version. Text field where you describe bug fixes, new features, or other changes for the release.
  • Privacy Policy URL. Link that points to your app’s privacy policy; Apple requires it for every submitted version.

08Things to know before you rely on it

  • Version numbers need to increase in order, for example 1.0 > 1.1 > 1.2.
  • The version entered in App Store Connect must be identical to the version embedded in the uploaded binary.
  • A build will not appear in the selection list unless it was uploaded through Xcode or Transporter with the correct version tag.

09If something goes wrong

  • Build not visible. Make sure the binary was uploaded using Xcode or Transporter and that its version matches the one you entered.
  • Version mismatch. Edit the version number in App Store Connect so it matches the version embedded in the uploaded build.
  • App rejected. Read the rejection reason from Apple, address the issue, and resubmit the updated version.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

The version number has to match the build version you uploaded, otherwise the update cannot be submitted.

After confirming the numbers, follow the App Store Connect steps, double check screenshots and the privacy policy before submitting.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about whitelabel mobile app updates.

Do I need a new Xcode build for every iOS app update?

Yes. Each update requires a binary uploaded via Xcode or the Transporter tool, and the version in the binary must match the version you enter in App Store Connect.

Can I change the app’s screenshots after it is live?

You can replace screenshots when you create a new version in App Store Connect. Updated images appear with the next released build.

What happens if Apple rejects my update?

Apple will provide a reason for rejection. Fix the issue, upload a corrected build, and submit the version again for review.

Is there a limit to how many times I can submit an update?

The article does not specify a limit; you can submit new versions as needed, provided each version number is sequential and a matching build is available.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.