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
- In HighLevel, select Launch App, then choose Generate Build and click Start App build.
- Wait until the build progress indicator shows completion.
- Open a web browser and go to App Store Connect.
- Sign in using your Apple Developer credentials.
- From the Apps Dashboard, click the app you intend to update.
- Inside the app page, press the Add New Version button.
- Enter the new version number that matches the uploaded binary.
- Ensure the version number is sequential (for example, 1.0 > 1.1).
- Provide a brief description of what’s new in this version.
- Replace screenshots or preview videos if the user interface has changed.
- Edit the description, keywords, or support URLs if required.
- In the Build section, click Select a Build before you submit.
- Choose the newly uploaded binary from the list.
- Save the changes you made to the version.
- Confirm that the Privacy Policy URL is correct.
- Answer any new questions in the App Privacy questionnaire.
- Verify all fields such as icon, screenshots, and metadata are accurate.
- 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
- Guide to promoting and customizing a whitelabel app Whitelabel app customization
- How to enroll an Apple Developer account for your whitelabel app Apple Developer enrollment
- HighLevel pricing and plans Pricing details
Michael's take

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.