Module · App Connector
App Connector: settings and screens
App Connector has two admin screens, both for administrators (manage_options) only:
- Mobile application (Мобільний застосунок): ExpertPress → Settings → Mobile application. Allowed apps, phone push, mobile features, status and emergency sign-out.
- Web push (Веб-пуші): WordPress Settings → Web push. Browser push notifications.
Options locked by the site
Every option on the Mobile application tab can also be set by a site filter named after it (expertpress_mobile_app_ids, expertpress_mobile_push_projects, expertpress_mobile_push_enabled, expertpress_mobile_commands_enabled, expertpress_mobile_editor_enabled, expertpress_mobile_account_enabled). A filter wins over the saved value. When one is active, the screen shows the filter name with “Site filter applied. Effective value:” and the value in use; for the app list it adds an Effective applications list. The access token can be fixed with the PHP constant EXPERTPRESS_EXPO_ACCESS_TOKEN in wp-config.php; the screen then shows Set by constant.
Mobile application tab
All fields in the first three panels are saved together with Save. The form is checked as a whole: if any row is invalid, nothing changes and you see “Settings were not saved completely. Check unique app IDs, UUIDs and token format, then try again.” While saving, the app list is emptied first and written last, so a failed save leaves app sign-in closed rather than half-open.
Applications
A table with one row per allowed application. Add application (Додати застосунок) adds a row; Remove deletes it. An empty row is ignored on save.
app_id
- Where: Settings → Mobile application → Applications
- What it does: Identifier of a branded app build that may sign in to this site. Use the
appIdfrom the build's brand profile, exactly as supplied with the build. - Default: empty list. An empty list blocks all mobile sign-in.
- Values / limits: up to 191 characters, case-sensitive, no spaces, control characters or markup; each value once.
- When to change it:
- You receive your first app build: add its
app_id. - You publish a second app (for example a separate specialist app): add a second row.
- You stop supporting an old build: remove its row. Its users lose app access on their next request.
- You receive your first app build: add its
- Related: EAS project UUID, Disconnect all mobile sessions
EAS project UUID
- Where: Settings → Mobile application → Applications
- What it does: Links the app to its Expo (EAS) project, which phone push needs. Copy it from the Expo project settings or from
extra.eas.projectIdin the build configuration; it must match the build. - Default: empty.
- Values / limits: a UUID such as
1b2c3d4e-0000-4a5b-8c9d-112233445566, or empty. Empty means sign-in works but this app gets no phone push. - When to change it: you are enabling phone push for an app, or the app was moved to another Expo project.
- Related: Enable push notifications
Push notifications
Enable push notifications
- Where: Settings → Mobile application → Push notifications
- What it does: Turns on phone push through Expo for booking, message, complaint and reminder events.
- Default: off.
- Values / limits: on / off. Push is actually sent only when this is on and a valid Expo access token is set; the panel shows Push transport is ready or Push transport is unavailable: enable push and set a valid token.
- When to change it:
- Turn it on once the app is published and the Expo token is in place.
- Turn it off temporarily if users report wrong or duplicate notifications while you investigate.
- Related: Expo access token, Web push
Mobile features
Each switch below turns one group of app actions on or off. When a switch is off, the app receives a “not available” answer for those actions; the website is not affected.
Booking commands
- Where: Settings → Mobile application → Mobile features
- What it does: Allows accepting, declining and cancelling bookings and setting meeting links from the app.
- Default: on.
- Values / limits: on / off.
- When to change it: an app release has a bug in booking actions; turn this off so people use the website until a fixed build is out.
- Related: The booking flow
Profile and service editor
- Where: Settings → Mobile application → Mobile features
- What it does: Allows specialists to edit their profile and services (including media) in the app. Edits still go through moderation as on the website.
- Default: on.
- Values / limits: on / off.
- When to change it: you want all profile and service edits to happen on the website, for example while you change moderation rules.
- Related: Specialists
Account actions
- Where: Settings → Mobile application → Mobile features
- What it does: Allows account actions in the app: changing account settings, resending the email confirmation and requesting account deletion.
- Default: on.
- Values / limits: on / off.
- When to change it: you want account changes and deletion requests to be made only on the website.
- Related: Clients
Expo access token
New Expo access token
- Where: Settings → Mobile application → Expo access token
- What it does: The secret the site uses to send through Expo. Create it in Expo account settings → Access tokens, and enable enhanced push security for the project in the EAS dashboard.
- Default: not set. The panel shows Token is set, Token is not set or Set by constant.
- Values / limits: write-only field, up to 4096 printable characters without spaces. Leave it empty to keep the stored token. Without a token, notifications wait in the queue and expire unsent.
- When to change it: first setup; after you rotate or revoke the token in Expo.
- Related: Delete stored token
Delete stored token
- Where: Settings → Mobile application → Expo access token
- What it does: Removes the stored token on save. Phone push stops.
- Default: off.
- Values / limits: cannot be combined with a new token in the same save. Hidden when the token is set by constant.
- When to change it: the token leaked, or you stop using Expo.
- Related: New Expo access token
Mobile status
Read-only panel.
- Mobile sessions schema v95, Command receipts schema v96, Push schema v97: Ready or Not ready. If any is not ready, app transport is on hold.
- Active mobile sessions and Active push devices: current counts, or Unavailable if they could not be read.
- Push queue — events from the last 24 hours: counts of
pending(including sending),ticket(sent, waiting for the delivery receipt) andfailed. - Last worker pass (UTC) for each background job. A pass may have found nothing to do; it is not proof of delivery.
Disconnect all mobile sessions
- Where: Settings → Mobile application → Disconnect all mobile sessions
- What it does: Signs every user out of the app. Website sessions are not affected. Sessions created after you press the button are not included.
- Default: — (an action).
- Values / limits: requires ticking I confirm disconnection of all mobile sessions. If it does not finish, the message says so; repeat it to finish.
- When to change it:
- You suspect app tokens were stolen.
- You replaced the app build and want everyone to sign in with the new one.
- Related: app_id
Web push page
Where: WordPress admin → Settings → Web push.
Send browser push notifications
- Where: Settings → Web push
- What it does: Sends the same events as phone push to browsers where signed-in users turned notifications on. When you switch it on for the first time, the site creates its own signing keys.
- Default: off.
- Values / limits: on / off. Users can turn notifications on only if your theme shows the browser notification settings block. On iPhone and iPad this works only for a site added to the Home Screen.
- When to change it: you have no app yet but want users to get booking and message alerts in the browser.
- Related: Enable push notifications
The page also shows Live browser subscriptions, Last full rescan lap and warnings:
- “Last web push error: …” with a hint (check the web push keys, the database and server log, or a user's browser subscriptions);
- “The rescan of live events has not finished a lap for over 12 hours; check that WP-Cron runs.”
Send a test notification to me queues a test notification for your own account through the normal pipeline. You receive it only if you turned notifications on in your own browser.
First setup checklist
- Install and activate ExpertPress, then App Connector. Check that Mobile status shows all schemas Ready.
- Add the
app_idof your build (and its EAS project UUID if you want phone push). Save. - Sign in from the app with a test client and a test specialist.
- For phone push: set the Expo access token, tick Enable push notifications, save, and confirm Push transport is ready.
- Optionally turn on Send browser push notifications under Settings → Web push and send yourself a test.