Goal

Click Publish to App Store or Publish to Google Play, and MAM Suite shows you a Publish status card at the top of the Publish Your App page. This guide walks you through reading that card, so you always know where each platform stands — submitted, in build, in review, or live — and you’ll recognize the moment something has stalled long enough to ask for help.

Prerequisites

• A WordPress admin account (the manage_options capability) on your MAM Suite site.
• Your app has already been submitted to at least one store. The Publish status card only appears for a platform once you’ve either submitted it or your app is ready to submit. If you haven’t submitted yet, see Submit your app for publishing first.
• An active MAM Suite subscription and account code. The status card reads from WP Mobile App Manager, so the account code must match the one on file for your site.

Where to find it

Open Mobile App Manager → Publish Your App in your WordPress admin. The Publish status card sits near the top of the page, above the setup checklist and the App Store Information settings. It shows one row per platform:

• App Store (iOS)
• Google Play (Android)

A platform’s row shows up only once you can publish to it, or once you’ve already submitted it. If a platform isn’t licensed or set up yet, and you’ve never submitted it, its row simply stays hidden — that’s expected, not a sign of trouble.

Steps

1. Identify each platform’s stage

Each row’s title tells you two things at a glance: which platform it is, and exactly what stage it’s at. You’ll see one of four broad stages.

Not yet submitted. The title reads “App Store — not yet submitted” (or “Google Play — not yet submitted”). Your app is ready and waiting — you just haven’t clicked the button yet. The row includes a Publish to App Store / Publish to Google Play button, right there for when you are.

Submission in progress. The title reads “… — submission in progress.” You’ve submitted, and behind the scenes your build is being created and uploaded to the store. The description underneath shows how long ago you submitted and roughly what to expect next — more on reading those timing cues in Step 2.

In review. Once your build is uploaded and TSL has moved it forward, the row lets you know your app has been handed to Apple or Google for review:

• iOS: “App Store — submitted to Apple for review.” Apple typically reviews within 1–3 days.
• Android: “Google Play — submitted to Google Play for review.” Google typically reviews within 1–3 days.

Published / live. Once your app is approved and live, the row reads “App Store — live in the App Store” or “Google Play — live on Google Play,” along with the date it went live. From here, the button becomes Publish another update, ready whenever you want to ship your next version.

Note: iOS submissions may pass through an in-between TestFlight stage (“App Store — uploaded to TestFlight”), and Android submissions may pass through a Closed Testing stage (“Google Play — pushed to Closed Testing”). Both simply mean the build is now installable by your internal testers, ahead of the public release. If you spot one of these, nothing’s wrong — your build is in testers’ hands and moving toward the store.

2. Read the timing cues on an in-progress submission

While a platform shows “submission in progress,” keep an eye on the description text underneath — it changes based on how long it’s been since you submitted, so you can gauge whether things are moving normally:

• Under 30 minutes: “Submitted X ago. Typically takes 20–30 minutes to process.” This is the normal window for a build to be created and uploaded.
• Under a day: “Submitted X ago. We’ll update this once the upload is complete.” Still within normal range — no action needed.
• Over a day: “Submitted X ago. This is taking longer than expected — contact support if you’d like an update.” This is your cue to reach out (see Step 4).

Every in-progress row also reminds you that builds run Monday–Friday, 6 AM–6 PM Central. Submit on a Friday evening or over the weekend, and the clock effectively pauses until the next business window opens — so if your submission sits “in progress” overnight or through the weekend, that’s expected, not stuck.

3. Refresh to pick up status changes

This status card reflects what WP Mobile App Manager reports for your site. That subscription/publish state is cached briefly — a few minutes at most — and refreshes each time you reload the page. So as your app moves from in-build, to review, to live, all you need to do is revisit or refresh Publish Your App to see the latest stage. There’s no button to click to “advance” things yourself — TSL moves your build forward through each store automatically.

4. Know when to contact support

Most submissions move through every stage on their own, with nothing needed from you. Reach out to support when:

• An in-progress row has been submitted more than a day ago (during business hours) and is still showing “submission in progress.” The card itself surfaces a contact support link at this point.
• A publish request failed outright — you’ll see a red “Publish request failed” notice at the top of the page rather than a status row. Re-check your developer-account connection and required-plugin status in the checklist below the card, then contact support if it persists.
• Your app has been “submitted for review” well beyond the typical 1–3 day window.

You can reach the team at wpmobileappmanager.com/support.

Related

• Submit your app for publishing — the steps that put a platform into “submission in progress.”
• Connect your Apple and Google developer accounts — required before a platform becomes publishable and its status row appears.
• Publish an update to a live app — using the Publish another update button once your app is live.
• Finish the publish checklist — resolving the App name, description, icon, and developer-account items that gate publishing.

What’s next

Once a platform shows live in the App Store or live on Google Play, go ahead and share your store listing, and start planning your first update. Every future release follows this same flow: click Publish another update, then watch this same Publish status card carry it from in-build, through review, to live.

Last verified against mam-main — includes/publish-app/app-submit.php (render_publishing_status, build_publish_status_row, publish_state_copy) and includes/helper-classes/mam-publish-status.php. Re-verify if the publish-state slugs, the in-progress timing thresholds, the “builds run” hours, or the status-row copy change.