Goal

Moved your WordPress site to a new domain? Switched from a staging address to your live one, flipped http to https, or changed hosts? Your published app needs to know where to find you now — and that’s what re-confirming enrollment does. It keeps your app registration pointed at the right address so your app can keep reaching your site without a hiccup.

Good news: it’s a one-click fix. Mobile App Manager notices the change on its own and shows you a notice in the WordPress admin — you just confirm it, and it handles the rest. You will not lose your account code or have to re-enroll from scratch.

When you’ll need this

When Mobile App Manager first enrolls your site, it saves your site’s address — specifically, the WordPress AJAX endpoint, derived from your site URL — and keeps that on file. From then on, every admin page you load, it quietly checks that saved address against your site’s current one. The moment they don’t match, it flags the change and waits for you — it never updates your account code on its own.

A few everyday situations will trigger the notice:

• You changed your WordPress Address under Settings → General (the address the app tracks follows this setting).
• You moved the site to a new domain.
• You switched the site from http to https, or added/removed a www prefix.
• You promoted a staging or development copy to production.

None of those match what you did, but you’re still seeing the notice? Check Troubleshooting below.

Prerequisites

• Your site is already enrolled with Mobile App Manager (it already has an account code). A brand-new, never-enrolled site enrolls automatically on its own and will not show this notice.
• You are signed in as an administrator. The notice and its button are only shown to users who can manage options (the WordPress manage_options capability).
• Your site can reach the enrollment server (wpmobileappmanager.com) over an outbound HTTPS request. The confirmation step calls out to that server to re-register your new address.

Steps

1. Open any page in the WordPress admin. Since Mobile App Manager checks for a URL change on every admin page load, the notice will be waiting for you at the top of the dashboard (or wherever you land) as soon as it spots the difference.

2. Find the “Mobile App Manager” notice. You’re looking for a yellow warning notice that reads, in effect:

   Mobile App Manager: Your site URL has changed from old-domain to new-domain. Click below to update your app registration.

   It shows both the old host and the new host side by side — a quick way to double-check the change is really the one you expected before you act on it.

3. Confirm the change is correct. Take a second to compare the old and new host shown in the notice against the move you actually made. If the “new” host looks wrong — say, it’s showing a staging domain you never meant to keep — stop here and fix your site address first; see Troubleshooting.

4. Click “Update Registration”. You’ll see a spinner while Mobile App Manager reaches out to the enrollment server and re-registers your site under its new address.

5. Wait for confirmation. Once it succeeds, the notice shows “Done. Your app registration has been updated.” and dismisses itself a couple of seconds later. Behind the scenes, Mobile App Manager has already saved the new address and cleared the pending-change flag — so you won’t see this notice again for this particular move.

6. If you see an error instead, the notice will let you know it couldn’t reach the enrollment server, and it re-enables the button so you can try again. Just confirm your site has outbound internet access first. Nothing is lost in the meantime — the pending change stays flagged until the update actually succeeds, so it’s safe to retry whenever you’re ready.

What this does (and does not) change

• Your account code is preserved. Re-confirming enrollment only updates the registered site address — it never issues you a new account code or detaches your existing one. The anchor for your production account stays intact across the move.
• It updates the saved site address. Mobile App Manager records the new address so future checks come up clean, with no mismatch.
• It clears the notice. Once the update succeeds, the pending-change flag disappears and the notice stops showing up.

Until you confirm, Mobile App Manager just keeps using the address it already has on file — it won’t switch on its own. That’s by design: it leaves the call to you, so a detected change that’s actually just a temporary or staging situation never gets registered by accident.

Troubleshooting

The notice keeps coming back. That means confirmation hasn’t succeeded yet — the pending change only clears once the update actually goes through. If the enrollment server couldn’t be reached, you’ll see the notice again on your next admin page load. Sort out the outbound-connection issue and click Update Registration again.

The “new” host shown is a staging or temporary domain. Hold off on confirming — if you confirm while your site’s on a domain you don’t actually intend to keep, that’s the address that gets registered. Instead, correct your site address under Settings → General first — once your site reports the address you actually want, the notice will reflect the right host and you can confirm then.

You don’t see the notice but expected one. Remember, it only shows up for administrators, and only once a real change has been detected. If your enrolled address and current address already match — say, because you confirmed the change earlier — there’s simply nothing left to do.

Your site is hosted on wpmobileappmanager.com itself. Sites on the source/enrollment host skip this notice entirely, to avoid a self-request loop, and are enrolled manually instead. So this one just doesn’t apply to you.

Related

• Building Your App: Enrolling your site with Mobile App Manager — how first-time enrollment and your account code work.
• Troubleshooting: My app can’t reach my site — when address or connectivity problems affect the published app.

What’s next

Once enrollment is re-confirmed, republish or refresh your app as usual so it picks up the current site address — then take a look and confirm your app screens are loading against the new domain.