Goal
When your site’s address changes, Mobile App Manager asks you one question: did this site move, or is it a staging copy? Your answer keeps the site connected to the right account on the Mobile App Manager server. A move never gives you a new account code, so your purchases, publishing and app stay with your site.
When you’ll see the notice
When Mobile App Manager first enrolls your site, it saves your site’s address (the WordPress AJAX endpoint, built from your WordPress Address). On every admin page load it compares that saved address with the current one. When the host (the domain name) is different, it shows the notice and waits for you. It never changes your account code on its own.
Typical reasons:
- You moved the site to a new domain, or launched it on its real domain after building it on a temporary or host-provided address.
- You changed the WordPress Address under Settings, General.
- You added or removed a
wwwprefix. - Your host made a staging or development copy of your live site.
A change of scheme only (http to https) or of path on the same host is recorded quietly. It does not affect your account, so there is no notice for it.
Prerequisites
- Your site is already enrolled (it has an account code). A brand-new site enrolls on its own and never shows this notice.
- You are signed in as an administrator (the
manage_optionscapability). Only administrators see the notice. - Your site can make outbound HTTPS requests to
wpmobileappmanager.com.
Steps
-
Open any page in the WordPress admin. The notice appears at the top as soon as the change is detected.
-
Read the notice. It says, in effect:
Mobile App Manager: This site’s address changed from old-host to new-host. Tell us which it is so your app stays connected to the right account.
Check that the old and new host match what you actually did.
-
Choose one button.
- This site moved to a new address. Use this when this is your live site at its new home. The server moves your existing account to the new address. Your account code does not change, so your subscription, publishing and plugins stay with the site.
- This is a staging copy. Use this on a copy of your live site (for example a WP Engine or Rapyd staging site). The server gives the copy its own staging account, linked to your production account. The copy switches to the staging account code. Your production site and its account are not changed. The copy remembers your production account code, and staging accounts share the production account’s publishing rights.
-
Wait for the result. On success the notice says “Done.” and closes a few seconds later. The new address is saved and the notice will not come back for this change.
-
If you see an error, nothing was changed on your site. The buttons come back so you can try again. Common reasons: the site could not reach
wpmobileappmanager.com, the server could not confirm this site owns the account, or you chose “moved” on a site that is registered as a staging account. If it keeps failing, contact support and include the message.
What each choice changes
| This site moved | This is a staging copy | |
|---|---|---|
| Account code on this site | Unchanged | Switches to the staging account’s code |
| Account on the server | Same account, address updated | New or existing staging account under your production account |
| Production site and account | This is the production site | Not changed |
| Subscriptions and publishing | Stay with the account | Production keeps them; staging inherits publishing from production |
Troubleshooting
The notice keeps coming back. The change has not been applied yet. Fix the error shown in the notice (usually outbound access) and choose again.
The new host is a temporary address you don’t plan to keep. If this is your live site and you are about to move it again, you can wait and answer the notice once the site is on its final address.
I picked the wrong button. Contact support. Do not hand-edit the account code.
My site is hosted on wpmobileappmanager.com. Sites on the enrollment server skip this check and are enrolled manually.
Related
- Troubleshooting: After moving or cloning my WordPress site, the app stopped working
- Troubleshooting: Publish Your App says my account code doesn’t match
What’s next
An app already in the stores calls the address that was built into it. If your live site moved to a new domain, publish a new build so the app uses the new address. Keep the old domain redirecting to the new one until your users have updated.
