Troubleshooting

Start on Overview. Check the player, chat input and request intake separately. A connection problem and a paused intake are different conditions.

Player will not connect

1. Open Pear Desktop and enable its API Server plugin.
2. Check Player API address in Connections. The default is http://127.0.0.1:26538.
3. Select Authorize PearConnect and approve the request in the player.
4. Select Test player connection.

If authorization expired, authorize again. Changing the player address clears the old credential. An idle player's empty current-track response can still be a successful connection.

If secure credential storage is unavailable, the desktop app stays open with a repair message. It does not save tokens as plaintext. Restore the OS credential facilities or use the separately configured CLI workflow.

TikFinity is connected, but requests do not arrive

• Confirm TikFinity Desktop is running on the same computer and connected to the livestream.
• Confirm Simple is selected if you expect direct event input.
• Check the WebSocket address; the default is ws://127.0.0.1:21213/.
• Compare Last event, Last chat message and Last command.
• Check the command name under Request rules and confirm intake is enabled.

An event timestamp with no chat timestamp can mean only non-chat events have arrived. An open socket alone is not proof of a functioning command route.

Requests are paused

Desktop launches, mode switches and reconnections pause requests deliberately. After testing the connections, select Enable requests in the top bar.

For the CLI, use --accept-requests or set REQUESTS_ENABLED=true after testing. New Simple setup files start paused.

A request was rejected

Result	Check
Cooldown	Wait for the viewer's cooldown to expire.
Duration unavailable	The enabled duration limit requires a known song length.
Song too long	Check Maximum song length.
Blocked	Review blocked phrases against the query, title and artist.
Forbidden	Check the appropriate request or skip allowlist and identity format.
Request limit	The viewer has reached the configured approximate tracking window.

The activity message gives more context. A rejection is not necessarily a connection failure.

Outcome uncertain

Check Pear Desktop before retrying. A request may have reached the player even if its response timed out or the connection failed.

PearConnect does not automatically retry player writes. Re-submitting a command or re-running a Streamer.bot action can create a new request.

Advanced integration fails

• Use Advanced mode in PearConnect.
• Set Streamer.bot's PearConnect.Url to http://127.0.0.1:7280, without /tikfinity, or use your configured port.
• Match PearConnect.Secret to PearConnect's webhook secret.
• Compile the imported C# actions and verify TikFinity's Streamer.bot connection.
• Run PearConnect's Test integration, then the imported Connection Test action.

The five actions have distinct endpoints. Read pearconnectOk and pearconnectCode, not only the HTTP status. See Advanced setup.

Another engine is already running

Close the other PearConnect desktop or CLI engine, then select Connect. Changing the HTTP port does not bypass the shared instance lock.

Opening a second desktop normally focuses the existing window. The app cannot yet attach its window to a running CLI engine.

No TikTok chat replies

Simple receives events only. Its replies appear in PearConnect. Advanced needs the separate chatbot relay. A successful song request does not prove a reply was delivered.

Ask for help

Open Activity & diagnostics → Preview report, review it, then select Export previewed report. The export omits credentials, identities, song/request text, configuration URLs, local paths and raw logs.

Open a GitHub issue with the app version, connection mode, observed result and relevant sanitized diagnostics. Don't paste tokens, an entire .env, or a private Streamer.bot argument dictionary.