claude-code - 💡(How to fix) Fix [Bug] Dispatch functionality not working across multiple devices (iPhone and Mac) [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/saifali/.local/share/claude/versions/2.1.97 (expected in multi-process scenarios)\n at Fd_ (/$bunfs/root/src/entrypoints/cli.js:2774:2153)\n at ua6 (/$bunfs/root/src/entrypoints/cli.js:2774:1233)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-09T19:30:20.334Z"},{"error":"Error: ripgrep exited with code null\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:528:2815)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-09T20:08:12.233Z"},{"error":"RipgrepTimeoutError: Ripgrep search timed out after 20 seconds. The search may have matched files but did not complete in time. Try searching a more specific path or pattern.\n at $ (/$bunfs/root/src/entrypoints/cli.js:531:242)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:531:456)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:528:2886)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-09T20:08:12.234Z"},{"error":"Error: ripgrep exited with code null\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:528:2815)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-09T20:08:12.400Z"},{"error":"RipgrepTimeoutError: Ripgrep search timed out after 20 seconds. The search may have matched files but did not complete in time. Try searching a more specific path or pattern.\n at $ (/$bunfs/root/src/entrypoints/cli.js:531:242)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:531:456)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:528:2886)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-09T20:08:12.400Z"},{"error":"Error: console.error: [bun] Warning: ws.WebSocket 'unexpected-response' event is not implemented in bun\n at K (/$bunfs/root/src/entrypoints/cli.js:523:10765)\n at emitWarning (ws:43:42)\n at #onOrOnce (ws:170:18)\n at FQ_ (/$bunfs/root/src/entrypoints/cli.js:3490:4680)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-09T20:24:05.362Z"}]

TL;DR

Try searching a more specific path or pattern to avoid ripgrep timeouts.

Guidance

• The errors suggest that ripgrep is timing out after 20 seconds, which may be due to a broad search query.
• Check the search path and pattern to ensure they are specific enough to avoid matching a large number of files.
• Consider updating the search query to narrow down the results and prevent timeouts.
• If the issue persists, try checking the file system permissions and access rights to the search directory.

Example

No code snippet is provided as the issue seems to be related to the search query and file system rather than code.

Notes

The provided errors indicate that the issue is likely related to the ripgrep search timing out, but the root cause may be specific to the user's environment or search query. Further investigation into the search query and file system may be necessary to resolve the issue.

Recommendation

Apply workaround: Try searching a more specific path or pattern to avoid ripgrep timeouts, as this is the most likely cause of the issue based on the provided errors.