Name the failure before changing the setup
“Remote not working” can describe several different faults. One phone might never appear, the wrong event might connect, or a previously connected remote might stop showing updates. Each observation calls for a different check.
Start with the rig stopped according to its instructions. Keep both screens visible and write down the last action that definitely succeeded. Do not start by reinstalling the app, deleting an event or changing every wireless setting: those actions can remove useful evidence and introduce another variable.
Use this decision table to choose the next check.
| What you observe | Check next | What the result tells you |
|---|---|---|
| The intended camera phone never appears | Open app/event, Local Network permission and shared network | Whether discovery has the prerequisites it needs |
| A phone appears but pairing fails | Current code, intended event and compatible app versions | Whether discovery succeeded but acceptance failed |
| The remote connects to an unexpected event | Event identity on both screens | Whether you are controlling the intended session |
| Connected status appears but a command fails | Camera readiness and the reported error | Whether the network is connected but the requested action is unavailable |
| A command was sent and confirmation disappeared | Actual state on the camera phone | Whether it started, is still running or finished |
| Recording works but no guest QR appears | Processing, upload and cloud-link status | Whether the problem is delivery rather than pairing |
This is a diagnostic method, not a promise that a particular setting fixes every failure.
Check local access, not just internet access
A phone can browse websites while an app cannot communicate with nearby devices. iPhone apps need permission to use the local network. Apple explains how to review this in Settings → Privacy & Security → Local Network. Check the intended app on both devices. Apple’s Local Network guidance.
Next, confirm the phones are using the network arrangement required by the app. A guest network may be configured to separate devices; Cisco Meraki documents client isolation as one example. Ask the venue contact rather than assuming the same Wi-Fi name guarantees communication. If you have an alternative network you are permitted to use, repeat the pairing check there without changing the event or app version at the same time.
A successful alternative-network test narrows the investigation. It does not prove a particular venue setting is responsible. Record the result so the venue technician or app support team can work from evidence.
Check the pairing details and version
Use the current details displayed by the intended camera event. A code saved in a message or remembered from a rehearsal may identify a different session. Confirm the event name after connection; do not rely only on the presence of a connected indicator.
Compare the app versions on both phones. If an app reports incompatible versions, follow its update guidance while you have a suitable connection and time to repeat the rehearsal. Do not make an untested update immediately before guests arrive simply because another version exists.
Keep the capture phone’s app open while checking. Note any permission, storage, entitlement or readiness message on that phone. A remote cannot make an unavailable recording action succeed merely by sending it again.
Treat an unconfirmed command differently
The most important distinction is between “the command was rejected” and “I do not know whether it arrived”. In the second case, repeated taps can make your understanding of the session worse.
Look at the camera phone. Is it counting down, recording, processing or showing a finished clip? Wait for the current action to complete or follow the app’s supported controls. Restore the connection from a known state before trying another recording. The physical motor remains a separate responsibility unless your exact integration documents otherwise.
Test the completed file as well. A confirmed start does not establish correct framing, a complete recording or a usable export. Our software selection checklist explains the wider acceptance test.
Keep delivery problems in their own branch
When the remote can control recording, a missing QR may be an upload or file-access problem. Check whether processing finished, whether the chosen cloud account is connected and whether a usable link exists. Avoid repeatedly pairing the phones to fix a stage that happens after capture.
Follow the QR delivery guide when the finished video exists but the guest cannot receive it. That separation prevents you from disrupting a working control connection unnecessarily.
Where SnapCircle fits
SnapCircle 360 uses a second iPhone as a local capture remote. Both phones need a common Wi-Fi network or hotspot and Local Network permission. Pairing uses the current event’s four-digit code; the app checks version compatibility and reports command state. This controls the recording workflow, not the arm’s motor.
For support, prepare a short record: phone models, iOS/app versions, network arrangement, displayed error, last confirmed state and one change you tested. Leave guest videos and account credentials out of a general support screenshot. That record is more useful than “it sometimes disconnects”.
If this control arrangement matches your booth, download SnapCircle for a pre-event rehearsal. The download is free; a subscription is required after onboarding. Complete a recording and handover before relying on the remote at a booking.
Published 5 November 2026. Guidance is based on documented capabilities and an operator checklist. Test your own equipment before a booking.