Home/HighLevel/Features/Mobile & Desktop App/HighLevel white label app build checklist fixing blockers

Mobile and Desktop Apps

HighLevel white label app build checklist fixing blockers

In short

The app build checklist runs inside Agency App Manager before a white label mobile app is compiled. It scans your Apple and Google store configurations, flags blockers that stop a build and warnings that do not. After correcting any issue, you re run the verification to clear the checklist.

AreaMobile & Desktop App · Whitelabel Mobile App
Used forMarketing agency, SaaS startup, Fitness studio
Setup steps7 steps in 2 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Agency owners, need to ensure each client’s store credentials and listings are correct before publishing the white label app.
  • SaaS Founders, must verify app identifiers and agreements so the platform can generate a functional mobile version for users.
  • Local service providers, use the checklist to confirm contact and support details are present, avoiding app store rejections.

02App build checklists, explained

The build checklist is part of Agency App Manager. It appears under Distribution > Channels when you select Launch App for a store. The view shows the number of issues, each with a Fix shortcut that opens the relevant store console.

Two result types appear: BLOCKER, which must be resolved before a build can proceed, and WARNING, which does not prevent the build but indicates optional or incomplete checks. The checklist runs independently for iOS and Android, so an issue on one platform does not affect the other.

After you make the required changes in App Store Connect or Google Play Console, you return to the checklist, tick the confirmation box, and click Verify. The verification must be run each time you modify a setting because results do not refresh automatically.

03How businesses use app build checklist

  • Marketing agency. The agency opens the checklist, follows the Fix links to update each client’s App Store Connect or Play Console settings, then confirms the changes in Agency App Manager and clicks Verify until all blockers disappear.
  • SaaS startup. The startup uses the checklist to confirm that its bundle identifier, service account JSON, and listing fields are correctly entered before generating the white label app for its customers.
  • Fitness studio. The studio ensures its contact information and support URLs are filled in the Personal info section, then re runs verification to clear any blockers that would stop publishing the app.

04Before you start

  • Apple App Store or Google Play Store credentials must be entered in Agency App Manager before the build checklist can run.

05How to set up and use app build checklist in HighLevel

Re run checks after fixing an issue

  1. Click the Fix shortcut beside the listed issue to open the appropriate store console and make the required change.
  2. Return to the App build checklist inside Agency App Manager.
  3. Check the box that confirms you have fixed the issue.
  4. Press Verify to execute the checks again; repeat as needed until the issue clears.

Verify after each change

  1. Tick the confirmation box.
  2. Select Verify.
  3. Wait a few minutes for any Google Play permission changes to apply, then verify again if needed.

06What it looks like in HighLevel

07Settings that matter

  • AppStore Connection. Stores the Apple API key, Issuer ID, and Key ID needed for the platform to communicate with App Store Connect.
  • App Setup. Holds the Bundle Identifier (Package Name) that must match the identifier registered in the Apple Developer portal.
  • PlayStore Connection. Accepts the JSON service account file that grants the platform access to the Google Play Developer API.
  • Personal info. Collects required developer contact details such as name, email, phone, and support URLs for the app store listings.
  • App Details. Contains the listing fields like app name, description, URLs, categories and distribution countries for each store.

08Things to know before you rely on it

  • You can hold up to 50 active Apple API keys at a time.
  • Bundle IDs are case sensitive; a mismatch stops the iOS build.
  • An Android package name is permanent and cannot be changed after the app is created in Play Console.
  • Service account permissions in Play Console may take up to 24 hours to propagate fully.
  • Google Play permission changes can require a few minutes before a re run shows the updated result.
  • The Firebase warning never blocks a build; it is informational only.

09If something goes wrong

  • The checklist still shows the issue after fixing it in App Store Connect.. Tick the confirmation box and select Verify. Wait a few minutes for any Google Play permission changes to apply, then verify again.
  • Uncertainty whether a warning stops the build.. Warnings do not block the build. You can continue building; resolve them later if desired.

10How it connects to the rest of HighLevel

Michael's take

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

The app build checklist is essential for getting a White Label Mobile App onto the stores without surprise failures. If you are not publishing a White Label Mobile App, skip it.

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

Common questions

Common questions about app build checklist.

How do I re run the checks after fixing an issue?

After correcting the setting in the store console, go back to the checklist, tick the confirmation box, and click Verify. Repeat until the issue no longer appears.

What is the difference between a blocker and a warning?

A blocker must be cleared before the app can be built; a warning does not prevent the build but indicates optional or incomplete checks.

Do I need to configure Firebase for my white label app?

No. Firebase is optional; the warning is informational only and does not stop the build.

Will an Apple issue stop my Android build?

No. The checklist runs separately for each store, so iOS problems do not affect Android builds.

Why must the Bundle ID and package name match exactly?

The platform matches your app to the store account using that identifier alone, and the match is case sensitive. Incorrect values prevent the build.

Who can accept the Apple agreements?

Only the Account Holder of your Apple Developer account can accept them; an Admin should ask the Account Holder to complete the step.

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.