HyperCam Trigger support

Get back to the shot.

Start with the camera, trigger or export path that failed. If the answer below does not solve it, send the exact message and device details to a person.

Start here

The shortest useful checks.

HyperCam is still in release validation. Physical-iPhone behaviour takes priority over Simulator output.

Camera preview is black, denied or never becomes ready

Open iOS Settings → Privacy & Security → Camera and allow HyperCam Trigger. Return to the app and try a manual capture before any trigger. If the session still does not start, close and reopen the app, check available storage and temperature, then report the exact readiness message. Simulator uses a demo path and cannot validate real camera behaviour.

Lightning, movement or sound fires too often

Start from the matching built-in preset. Lower sensitivity, add cooldown, keep the iPhone stable and remove moving reflections, screens or branches from the analysis area. For Lightning, aim only from a safe sheltered place and use the sky guard or a selected zone when available. For Sound, separate a sudden event from constant background noise.

A trigger arms but misses the moment

Confirm the shutter reports ready, use a fast capture profile, avoid unsupported high-quality combinations for the first test and keep storage and thermal state healthy. Some RAW, bracketed, flash, maximum-resolution or boost workflows trade speed for quality. A trigger request cannot guarantee the final frame.

Sound or keyword mode cannot start

Allow Microphone access for sound-level triggers. Keyword detection also needs Speech Recognition access and Apple Speech availability for the current language. HyperCam waits until the audio engine genuinely starts before treating the route as armed. Apple may process keyword audio on its servers.

The capture is local but not in Apple Photos

This is expected by default. HyperCam saves to its internal gallery first. Use the explicit Photos export button and allow add-only Photos access when prompted. Deleting a local item does not delete a copy already exported to Photos.

Cloud Upscale fails or asks for configuration

Cloud Upscale is optional and requires a compatible HTTPS endpoint and, where needed, a provider token. Run the in-app contract test, confirm the provider's request format and use a non-sensitive test image. Never email an API key. The chosen provider, not HighRoad, controls its service availability and data handling.

Lock Screen, Control Center, Action Button or widget route does not appear

Confirm the iOS version supports that surface, add the HyperCam widget or control from the relevant system editor, and launch the main app once so iOS can register current intents. The Locked Camera Capture path requires iOS 18. Availability can vary by device, system settings and the final shipping configuration.

How do I buy, cancel or restore HyperCam Pro?

The public App Store products are not live yet. Once available, the Apple purchase sheet will show the current regional price and renewal terms before confirmation. Manage a subscription in Apple ID → Subscriptions. Use Restore Purchases in HyperCam while signed in to the Apple ID used for the eligible purchase. For refunds, use Apple's Report a Problem service.

What should I include in a bug report?

Send the HyperCam version and build, iPhone model, iOS version, trigger mode and preset, steps to reproduce, expected result, actual result, exact message and whether the issue repeats. Attach a redacted field diagnostic or short screen recording only when useful. Remove faces, private locations, photo content, endpoint tokens and unrelated device data.

Privacy and legal

Know the data boundary.

Local captures, Apple services and a user-configured provider are different paths.

Still stuck?

One clear report beats ten guesses.

Write to HighRoad support. The support page and mailbox are public and do not require an account.

Email HyperCam support