Skip to content

Troubleshooting ​

Find the symptom below, or start with tapflow doctor on the Mac where it happens.

Start with tapflow doctor ​

On the agent Mac, tapflow doctor checks Node.js, the port, Xcode and the simulator, the Android SDK and an AVD, and prints what to fix for each failure. Pass ios or android to check one platform. The checks are listed in the CLI reference, and each failure is explained under tapflow doctor failures.

sh
tapflow doctor
tapflow doctor ios

Find your symptom ​

SymptomSee
An agent does not appear in the dashboard, or cannot connectAgent cannot connect to the relay
tapflow agent start says an agent is already runningIt says an agent is already running
The relay reads a configuration or database you did not expectUnexpected configuration or database
Opening an iOS build fails with spawn unknown erroriOS simulator
The iOS simulator does not bootService version mismatch, cannot be located on disk
The Android stream does not startAndroid emulator
An upload fails with 400Builds & uploads
An APK does not install on an Apple Silicon Mac (INSTALL_FAILED_NO_MATCHING_ABIS)Builds & uploads
The stream lags, stutters or looks blurryStream & sessions
A session ends by itselfSession ends automatically
A device will not go offlineNetwork control
An invitation or password reset link does not workSign-in & accounts
Everyone was signed out after an upgradeSigned out after upgrading

View the relay's logs ​

On the relay host, inspect its activity with the commands below. The relay does not show its logs to other machines.

sh
tapflow logs
tapflow logs --lines 200

Running under Docker, a CLI outside the container counts as remote; use docker compose logs instead.

Moved sections ​

Sections that used to be on this page now live on these pages.

Released under the MIT License.