Troubleshooting
What the messages mean and what to do about them.
Messages

Problems appear in an Attention box on the screen. The serious ones — a phone that has stopped recording, a microphone that would not start, a stack that would not build — also show as a red banner under the strip along the top, on every session screen, and the phone buzzes when one arrives (unless haptics are off in Settings › Sessions). Where there is something the banner can do about it, it has a button: Open Settings when the microphone is off, Huddle again when the microphone changed or the sweep did not play.
The box says what happened in a sentence. The technical side — the error itself, what the audio system was doing — goes to Settings › Problem log, which keeps every problem with its time. If you report a problem, Share there sends the log as text.
Tap ✕ on a message once you've read it, or Clear all when there is more than one. A cleared message comes back if the problem happens again.
Before you start
If something on this phone would get in the way of recording, Before you start appears on the home screen, with what it is and what to do: the microphone is off, the phone is nearly full or too hot, the battery is low and it is not charging, or Low Power Mode is on. A phone with nothing wrong shows nothing there at all.
In the lobby, the host is also asked about the other phones: one that is nearly flat is listed with the others that could spoil a take, and the host can carry on anyway.
Joining

"That join code does not match this session." Check the code on the host's screen and enter it again.
"The session is full." The session has reached its phone limit, or the host has marked it full. Ask the host to raise Up to … phones or turn off Full — no more phones.
"The host removed this phone from the session." This phone can't rejoin that session.
"This phone's version of StakdTrax cannot join this session." Every phone needs the same version of StakdTrax. Update them all.
"This phone is already in a session, so it did not join …" A scanned code only joins from the home screen. Tap End first, then scan again.
A phone stays on "Looking for the session". It can't see the host at all. Check that Wi-Fi and Bluetooth are switched on in Settings on both phones — not just in Control Center, and not in Airplane Mode — that the code is right, that the phones are close, and that both have a recent version of StakdTrax — a much older one can't see sessions on a newer one. No Wi-Fi network is needed. After twenty seconds of nothing, StakdTrax says so itself and points at Settings › Privacy & Security › Local Network — the one permission that, if declined, looks exactly like this at any distance, and which nothing else in the app can tell apart from a host that is merely out of range yet.
A phone keeps saying "Couldn't connect — trying again". It can see the host but the connection isn't completing. This is a different problem from the one above: discovery is working, so it isn't the radios or Local Network permission. The fix that works is to put the phone on the same Wi-Fi network as the host, or on the host's Personal Hotspot — on a shared network phones connect at the first try. Otherwise, keep the phones within a few metres of each other and leave it to keep trying. If a phone is sharing a Personal Hotspot that nobody has joined, try turning it off.
A session doesn't appear under Open sessions nearby. It may be closed — ask the host for the code. Keep the phones close together, make sure Wi-Fi and Bluetooth are on, and check that StakdTrax is allowed to use the local network in Settings › Privacy & Security › Local Network.
Calibrating and recording

A phone shows "not synced" with a red dot. Its clock hasn't agreed with the host's yet — give it a few seconds with the phones close together. no timing packets means nothing is getting through at all; check Wi-Fi and Bluetooth. If it counts exchanges but still doesn't sync, the connection is poor — move the phones closer.
The phones lose each other when you spread out. Often Wi-Fi being switched off on one of them. The phones find each other over Wi-Fi even with no network to join and no internet — but with the radio off they fall back to Bluetooth, which carries only a few metres, so the session holds while you are huddled for calibration and drops as soon as you separate. Turn Wi-Fi on in Settings on every phone; you do not need to join anything. If Wi-Fi is already on everywhere and this still happens, the phones are simply too far from the host for where you are. Put the host in the middle of the group, get phones out of pockets, or use a Wi-Fi network that covers the space — see Before everyone spreads out. If Wi-Fi genuinely can't be used on one, the host can share the session over a Personal Hotspot — see Hosting a session.
A phone's row says "offline · 4 min". The number is how long it has been gone. Seconds usually means a phone that will find its way back; minutes means going to get it. It keeps recording either way, and its takes come over once it's back.
A phone says "Lost contact with the host". It has gone out of range, or its screen locked. It keeps recording and keeps trying to reconnect. Bring it closer to the host, and tap Reconnect if it doesn't find its way back. Its takes are sent to the host once it's back — see If a phone loses the host.
iOS offers to swap contacts during the huddle. Hold the phones bottom to bottom with the tops apart — see Calibrating.
"The calibration sweep did not play." Check the primary phone's volume and that nothing else is playing sound, then tap Play the sweep again.
A phone says "needs recalibrating". Its microphone changed after calibration. Calibrate again before recording.
"The microphone could not be started." Another app may be using the microphone, or the audio route changed. Close other audio apps and try again.
A phone was never collected from, and the session is over. Its take is still on it. Bring both phones into a session together — any session, as long as the same phone is hosting — and the phone with the take lists it under Takes still to send in the lobby. Sending it puts it back with that session's other tracks, and the host can rebuild the stack. See If a phone loses the host.
A take is listed under "The host no longer has these sessions". The host deleted the session it belongs to, so it can't be sent back. It's still on the phone that recorded it — share it from there, or tap Stop offering to clear it from the list. Stopping doesn't delete the recording.
Collecting
A track says "no progress". The transfer has stopped moving. Bring that phone close to the host, make sure its screen is on, and tap Restart on the row to send the take again from the start.
"Could not collect from …" That phone couldn't send its recording after three tries. Bring it close to the host and tap Retry on its row. If it still won't come, the recording is still on that phone — share it from the Files app, under StakdTrax.
Permissions
"Microphone access was declined." Turn it on in Settings › Privacy & Security › Microphone.