Setup & support

Before you begin

You need a compatible Nevar Bridge JSON API v1 receiver, its HTTPS base address and a device token issued by its administrator. A normal website URL alone is not a receiver. Nevar Bridge does not supply a hosted tracking account.

For developers, the API guide describes all three endpoints and the configuration-import format.

Set up your first connection

1. Add or import a server

   Tap Add server for manual setup, or Import pairing to choose an administrator-provided JSON file. Pairing files contain credentials; keep them private.

2. Make it your connection

   Enter a connection name, primary HTTPS base URL and bearer token. Optionally set Your name for this connection and a map color. A receiver may use these to display you; support depends on that receiver.

3. Choose routes and an interval

   An alternate HTTPS address must reach the same receiver with the same token. Use it for a local-network route if appropriate. Choose a 5, 10, 30 or 60-second update target; it is not a guaranteed timer.

4. Save, then test

   Tap Save → Test connection. This verifies authentication and a compatible response without sending coordinates. Fix any token, address or certificate errors before sharing.

5. Choose your sharing name

   Enter a name in Your sharing name. This is your default for connections without their own name. Names are chosen labels, not account logins or verified identities.

6. Start sharing

   Enable the intended destinations and tap Start sharing. Allow location access and check each connection’s Last accepted time. Add up to three independent destinations.

Location and background permissions

On the first iOS prompt, choose While Using the App. Turn on Precise Location if you want precise reports. To request Always access, open Privacy & help → Request Always location access. iOS handles that upgrade separately; you can also review permission in iPhone Settings.

During an active session, background location can continue while the screen is locked. Keep sharing enabled and do not swipe the app away. iOS controls scheduling and can interrupt background activity. Reopen the app after a phone restart. Always permission does not guarantee uninterrupted reporting or relaunch after force-quit.

Offline queues and reconnection

When a server cannot be reached, its reports remain queued independently. The app retries with increasing delays. A restored network can trigger another attempt, but server-requested cooldowns are respected.

On reconnect, the newest queued report goes first, followed by older reports with their original measurement times. The receiver must keep historical reports separate from live positions.

A nearby server can receive updates without internet if your phone can reach it over a local network and HTTPS trust is valid. A VPN-only server needs its usual VPN connection. The app does not create either network.

Troubleshooting

Stop, clear or remove

Stop sharing pauses GPS collection and queued uploads. It retains the queue. The stop notice to a receiver is best effort: an unreachable server cannot immediately learn that you stopped.

Use a connection’s menu to Clear queued positions or Remove destination. Removing a destination clears its local queue and token. These actions do not erase reports already accepted by a server; contact that server’s administrator for deletion or token revocation.

Common questions