Apple and Google both need a way to recognize your app as your app — that’s the job of your bundle IDs, Team ID, and channel. Every build, push notification, and store submission ties back to these values and your developer accounts. Here’s what each one is, where you’ll find it in MAM Suite, and how it gets set.
Short version: In the current MAM Suite, WP Mobile App Manager (WPMAM) manages these identifiers for you and shows them read-only on the Publish Your App page. You won’t normally type them in yourself — they’re provisioned when your app is set up on the WPMAM side, once your Apple and Google developer accounts are connected. This article walks you through what they are, so you can confirm they look right before you submit.
Before you start
You should have already:
- Purchased a publishing plan (the Publish Your App page confirms this with a
can_publishcheck against WPMAM before it will let you submit). - Created or applied for an Apple Developer Account (Company/Organization) and a Google Play Developer Account, and invited the MAM team.
- Connected your site to your account so the account code verifies on the Publish Your App page.
If anything on that list isn’t done yet, work through the App Publishing Wizard first (Run the app publishing wizard end-to-end), then come back here.
What each value is
| Value | Identifies | Format / example | Set by |
|---|---|---|---|
| iOS Bundle ID | Your app on the Apple App Store | Reverse-domain, e.g. com.yourcompany.yourapp |
WPMAM (system-managed) |
| Android Bundle ID | Your app on Google Play | Reverse-domain package name, e.g. com.yourcompany.yourapp |
WPMAM (system-managed) |
| Team ID | Your Apple Developer organization | 10-character alphanumeric, e.g. A1B2C3D4E5 |
WPMAM (system-managed) |
| Channel | The build/release channel for this app’s iOS builds | Short internal label | WPMAM (system-managed) |
Bundle ID (iOS and Android). Think of it as your app’s fingerprint in each store — a unique, reverse-domain identifier. Once you publish under a bundle ID, that ID is locked in for good: it’s how the store recognizes a new upload as an update to your app rather than a brand-new listing. iOS and Android can use the same string, but each store tracks its own copy.
Team ID. This is the 10-character identifier for your Apple Developer account — your “team,” in Apple’s terms. It tells Apple, and the build pipeline behind the scenes, which developer organization owns your app and its signing credentials.
Channel. This one’s just for us: an internal label MAM Suite uses to route your iOS app to the right build/release channel in the publishing pipeline. Apple and Google never see it — it’s bookkeeping for the WPMAM build system.
Where to find them
- In WordPress admin, open Mobile App Mgr → 🚀 Publish App (the Publish Your App page).
- Behind the scenes, the page checks your account code against what WPMAM has on file for this site’s URL — a safeguard that keeps a build from ever getting misrouted to the wrong account.
- Scroll down to the App Identifiers & Versions panel — a read-only reference panel showing:
- iOS Bundle ID
- Android Bundle ID
- Team ID
- iOS / Android version numbers
- iOS / Android build numbers
A note under the panel reads: “These values are automatically managed by WP Mobile App Manager and are shown for reference only.” The fields are visible but disabled — they’re there for you to confirm, not edit. Any value that hasn’t been provisioned yet shows a placeholder dash (—).
The channel value doesn’t get its own visible field in the current Publish Your App UI — it’s stored alongside the iOS identifiers and submitted along with your build. If you need to confirm the channel for your app, just contact the MAM team.
How they get set
When you save and submit on the Publish Your App page, MAM Suite assembles a settings payload — the bundle of data handed off to the build system — and sends it to the WPMAM build pipeline (Fastlane-driven CI). Here’s where each identifier lands, stored as a WordPress option:
| Value | Option key |
|---|---|
| iOS Bundle ID | ios_pn_app_bundle_id |
| Android Bundle ID | android_pn_app_bundle_id |
| Team ID | ios_pn_team_id |
| Channel | local-app-ios-app-channel |
These option keys are frozen: they predate MAM Suite’s current naming convention, and they stay that way on purpose. Renaming them would sever the link between your site and your existing Apple/Google submissions, so nobody touches them casually.
In practice, that works in your favor: instead of asking you to type in a bundle ID and risk a typo that breaks signing or store matching, MAM Suite has the WPMAM team provision these once, correctly, when your app is created — then simply shows them back to you to confirm.
Confirm before you submit
Before you click Submit Publish Request, glance at the App Identifiers & Versions panel and check:
- Both bundle IDs are present (not showing a dash) — a missing bundle ID means the app hasn’t been fully provisioned yet.
- The Team ID is present and is 10 characters — a blank Team ID usually means your Apple Developer account isn’t connected on the WPMAM side yet.
- The bundle IDs match your existing live app, if you’re publishing an update rather than a first release — a changed bundle ID would make the stores treat the upload as a brand-new app.
If anything looks off or missing, don’t force the submission. Account-code and identifier mismatches aren’t something you can fix from this page — reach out to the MAM team and they’ll set things right at the source.
Why you can’t just edit them
These fields are read-only on purpose:
- A mistyped bundle ID silently breaks the store’s ability to match an update to your live app.
- A wrong Team ID breaks code signing, and the build fails late in the pipeline.
- The option keys are part of a frozen contract with deployed apps; the value behind each key has to stay in lockstep with what Apple and Google already have on record.
Keeping them system-managed heads off the most common — and most expensive — class of publishing mistake before it ever happens.
Related articles
- Run the app publishing wizard end-to-end
- Create an Apple Developer Account and invite the MAM team
- Create a Google Play Developer Account and invite the team
- Set your app name and icon background
- Fill in App Store and Google Play listing info
- Submit your app to the App Store and Google Play
- Track your publish status after submitting
