Transfer fails / Peer is taken offline mid-transfer

What seems to be going wrong?

I am experiencing a one-way file transfer failure between my Mac and my Google Pixel 7 phone.

• What works: Sending files from the phone (via cellular network/Tailscale) to the Mac works perfectly fine; the Mac client receives files successfully.
• What fails: Sending files from the Mac client to the phone constantly fails.

The targets/devices can discover each other successfully, and they are properly paired. However, whenever I initiate a file transfer from the Mac to the phone, it instantly fails or gets stuck, though it occasionally succeeds out of sheer luck. This issue is not new and has been persistently occurring since version 0.60.

How can we reproduce this?

1. Install DashBeam v0.62 on a Mac running macOS Monterey 12.7.6, and on a Google Pixel 7 running Android 17.
2. Pair both devices. Keep the phone connected via a cellular network utilizing the home Tailscale mesh setup.
3. Successfully send a file from the Pixel 7 to the Mac to confirm the one-way path is working.
4. Attempt to send a file from the Mac back to the Pixel 7. The transfer will fail or time out, despite the phone being fully discoverable as a target on the Mac UI.

Your environment

• DashBeam version: v0.62
• OS and version (e.g. macOS 14, Windows 11, Fedora 41, Android 14): macOS Monterey 12.7.6 (Mac) & Android 17 (Pixel 7)
• How you installed it (.AppImage, .deb, .rpm, Flatpak, .msi, .exe, .dmg, .apk): .dmg on Mac, .apk on Android
• Did it work in an earlier version? If so, which: No, this issue has been present since v0.60.

If the problem involves sending or receiving files, please also tell us:

• The other device's platform and version: Google Pixel 7 (Android 17)
• Relay mode (Settings → Network → Relay servers), Automatic / Custom / Disabled: Automatic
• Does Test connection succeed on both devices? The phone can ping and connect to the Mac, but the Mac fails or intermittently times out when initiating a reverse connection to the phone over the network translation layer.

If the problem is visual (a blank window, rendering glitches, missing UI) and you're on Linux:

• Desktop environment, and Wayland or X11 (echo $XDG_SESSION_TYPE): N/A
• Graphics hardware (fastfetch --pipe or inxi -GSx): N/A

Logs

dashbeam.log

dashbeam-diagnostics-2026-07-30-22-02-17.txt