| Problem |
Try this |
| Find my Core does nothing |
Turn Bluetooth on. Allow the app to use Bluetooth (and “Nearby devices” on Android) when it asks, or in your phone’s settings. |
| “Bluetooth needs a development build” |
Your copy of the app cannot use Bluetooth, for example Expo Go. Tap your rolls in by hand, or ask the team for the full test app. |
| It connects on the second try |
That is normal on some Android phones. The app tries again by itself. |
| It keeps disconnecting |
Keep the Core within a couple of metres. Check its battery on My Core. |
| Problem |
Try this |
| No email |
Wait a minute. Check spam or junk. |
| “Not recognised” |
Use the exact email from your invite. Only invited emails work. |
| The code is refused |
Codes run out quickly. Ask for a new one and use the newest email. The code has 6 or 8 numbers. |
- Wake the Core: give it a gentle shake.
- Check it is charged.
- Make sure no other phone is connected to it. A Core talks to one phone at a time.
- Close the app fully and open it again.
- Still nothing? Try Try demo mode to check the app works, then tell the team.
“On an edge” means the Core did not land flat. It never counts. Roll again.
| If it happens… |
Try this |
| now and then |
That is normal: just roll again. |
| often |
Roll on a flat, hard table, not a cloth or a bed. |
| on flat rolls, or the wrong face shows |
Calibrate again on My Core: tap Calibrate and capture all 12 faces. |
| Problem |
Try this |
| Waiting for ever |
Check everyone has sent their roll. The app lists who is still waiting. |
| You closed the app |
Open it again. It takes you back to your Siege or match. |
| Someone has gone |
In a Siege, anyone can pause. If they do not come back, a ghost takes their place. |
| A Siege is truly stuck |
Ask the team. They can cancel it. A cancelled Siege changes nothing. |
