Pocket Core connection

Pocket Core is optional. Settings → Services has Pocket Core and Individual services tabs on iPhone, Mac and Android. The list below follows the selected mode: Core shows only services supplied by your pairing; this applies to Home, tabs, search, shortcuts and service requests as well as Settings. Individual services shows the full manual catalogue, with configured services first. There is one Services entry in Settings, not a separate connection page. Existing manual setups continue using individual services. You can switch between the two without erasing saved service credentials.

Pair this device

1. Generate a pairing code in your Pocket Core account.
2. Open Settings → Services → Pocket Core. On first run, choose Connect with Pocket Core, or open the configuration import screen and choose Pair with Pocket Core.
3. On iPhone, tap Scan QR code and allow camera access, then point at the pairing QR code displayed in Core. Scanning fills the address and code and returns to the form. If scanning is unavailable, use Paste for a copied pairing link, or enter the HTTPS address and code manually. You can also use the iPhone Camera app to scan and open the link. On Mac, paste or open the link. Enter a device name. Scanning or opening a link never pairs automatically.
4. Check that the address is your Core server, then choose Pair this device.

Core supplies the service settings available to your account. Pocket Money, Garage, Documents, Podcasts and Notes profiles select their Pocket providers in those shared service slots. Pair each device separately. Pairing does not install servers or change the app’s service limits.

The address must use HTTPS with a certificate the device trusts. Credentials, query strings and fragments are not accepted in the Core address. Pairing codes and device credentials are secrets; do not include them in screenshots or reports. The device credential and saved configuration stay in the platform’s secure credential store (Keychain on Apple).

Switch connection modes

• Individual services restores the manual values that Core replaced, while keeping manual edits. Configure services in Settings → Services as before. The pairing is retained securely, but explicit and foreground Core refreshes are paused. Core-only values disappear from the active configuration when there was no previous manual value.
• Pocket Core reuses the saved pairing and refreshes its profile. No new code is needed unless the credential was revoked or the pairing was disconnected. Manual changes made while paused are saved for the next switch back.

In Individual services, each service can offer its own application choice. For example, Settings → Services → Garage has Pocket Garage / LubeLogger tabs. In Pocket Core, the provider and connection details come from Core and are read-only on the device. Pocket Garage owns its Money transactions on the server when that integration is enabled; the app does not create a second transaction. LubeLogger retains its existing optional payment-entry flow.

Core-managed services

Open a connected service to see its supplied address, connection status and a Test connection action where supported. Open Pocket Core takes you to Core for changes. Address fields, credentials, provider choices, local enable switches and removal actions are unavailable while Core is selected.

Refresh services fetches Core’s current profile; returning to the foreground also refreshes it. When Core removes or disables a service, that service disappears from Home, tabs, search and shortcuts, and its saved manual credentials are not used for service requests. Core-supplied addresses and credentials take precedence in Core mode, including over overrides made in earlier app versions. A failed network refresh keeps the last successfully saved profile.

Manual configuration stays securely stored for Individual services. Changes made there remain available on the next switch back. Disconnect restores those manual values. Changing modes does not erase downloaded content or local data.

Disconnect or revoke

Disconnect on this device removes the local pairing and restores settings that Core replaced, preserving manual edits. It does not revoke the credential on the server. Revoke a lost or retired device in Core to invalidate its token.

If Core rejects an active device credential during refresh, the app disconnects locally and restores the same manual settings. A paused pairing is checked when you switch back to Core. A new pairing code is then required to reconnect.

Configuration imports and transfer

Manual entry, env import and encrypted device transfer remain available. A Core QR link carries a pairing request, not a full configuration export. Saved configuration can only be exported sealed under a passphrase. Prefer a separate Core pairing for each device so that it can be revoked independently.