Troubleshooting

The most common cause: iOS notification permissions were denied for BRYKK.

1. Open the iOS Settings app (not BRYKK)
2. Scroll to Notifications
3. Find BRYKK in the list
4. Make sure Allow Notifications is ON
5. Make sure Lock Screen, Notification Center, and Banners are all checked
6. Review Focus and notification delivery settings. Time Sensitive notifications and Critical Alerts are different permissions; only use the options iOS actually shows for BRYKK.

Common causes:

• Their phone is off. The map may retain the last shared location. A final update before shutdown is not guaranteed.
• A connection or sync issue. Coverage is one possibility, not the only explanation. Compare the sender's and viewer's update times and report repeated delays.
• The app is not running normally. When it is safe to do so, open BRYKK on the sending phone and check its permissions and family connection.
• Background updates were delayed. Device state and system scheduling affect delivery. Request update is a request, not a guarantee of an immediate new fix.
• Location permission downgraded. Have them check Settings → Privacy → Location Services → BRYKK → make sure it's set to Always.

The family map frames shared locations, which may include older positions. Read each member's update time before assuming a pin is current. To explore:

• Pinch and drag to where you want
• Use the family overview to check who is at a saved place or moving
• Tap any family member's avatar in the off-screen stripe to fly the camera to them

If you still see duplicate places, swipe-left on the extras and delete them manually. Newer builds are much better about warning before duplicates are saved in the first place.

Going forward, BRYKK warns you before saving a duplicate: “Work is already saved within 50m of this location. Save anyway?”

First decide which case you're in: is this your own iPad, or a separate family member's iPad? BRYKK supports both, but the fix is different.

• Your own iPad: confirm it is signed into the same Apple ID as your iPhone and that iCloud Drive is on
• Someone else's iPad: install BRYKK on that device and join the family normally with the family code
• If the iPad still looks empty, open BRYKK on it again and let it finish syncing before force-quitting or reinstalling

BRYKK works on iPhone, iPad, Apple Watch, and Apple TV — but the location accuracy depends on the hardware in each device, not on BRYKK. Setting expectations honestly:

• iPhone — use the phone a person carries as their primary sharing device. Buildings, surroundings and device settings can affect accuracy.
• Cellular iPad — capabilities vary by model. A location fix is not a guarantee of a specific building or business, especially where places are close together.
• Wi-Fi-only iPad — treat it primarily as a household viewing screen, rather than a substitute for the phone someone carries. Check accuracy and update time instead of assuming every point is precise.

A few iOS behaviors are out of our hands and worth knowing about so they don't surprise you:

• Always Location is required for arrival, departure, dead-zone resume, and impact-detection logic. “While Using” only is enough to openBRYKK, but most family-safety features won't fire when the app is backgrounded or the screen is locked.
• Force-quitting can interrupt background sharing. Reopen BRYKK and check for a new shared update. Do not assume reopening alone guarantees delivery.
• Low Power Mode and Low Data Modecan both delay BRYKK pushes. Apple throttles silent CloudKit pushes hard in either mode. We've designed around it where we can, but a phone in Low Power Mode is going to update less often.
• Carrier and Wi-Fi dead zones can delay updates. Recovery still depends on the app and device being able to upload; missing samples cannot always be reconstructed.

If this still happens, update to the newest BRYKK build first. Older builds had audio-session issues that could interfere with music playback.

If you're still seeing it after updating, force-quit BRYKK and reopen. If the bug persists, email us and include the device plus car setup.

Three things have to be true for the Coming Home alert to fire on the receiver:

1. The receiver is at the saved place that matches the sender's destination (cityState = “At Home”)
2. The receiver has “Coming Home to You” toggled ON in Settings → Notifications → Location
3. The sender actually started a trip with the destination set (tap Go on Home from the search bar, or CarPlay-triggered driving with destination)

If the sender just starts driving without setting a destination, the regular “On the road” flow runs instead — no Coming Home alert because BRYKK doesn't know where they're heading.

Email us at support@brykk.app with:

• What you tried to do
• What happened instead
• Your iPhone model + iOS version
• BRYKK version (Settings → About → Version)