Device Discovery Failed

Use this page when Nearby Sync cannot find another device.

Not sure this is the right page? Use the minimal test in the Troubleshooting overview to find the layer first.

Fast checklist

1. Open Octoclip on both devices.
2. Put both devices on the same trusted network or supported local path.
3. Disable guest Wi-Fi, AP isolation, VPN, proxy, or firewall rules temporarily for testing.
4. Confirm local network permission where the OS asks for it.
5. Confirm both devices use Nearby Sync, not one Nearby and one Cloud-only setup.
6. Test with a short text clip.

Network causes

Nearby discovery can fail when the network blocks local device-to-device traffic. Enterprise networks, hotel Wi-Fi, guest Wi-Fi, and VPNs commonly block this.

Platform causes

• Windows: firewall, network profile, store sandbox behavior (Bonjour/mDNS only on older versions).
• macOS: local network permission, firewall, Focus or sleep behavior.
• Android: local network/Wi-Fi permissions, vendor background restrictions.
• iOS/iPadOS: local network permission and foreground/background limits.

Workaround

If local discovery is blocked and you cannot change the network, use Cloud Sync through WebDAV / S3 on activated paid devices.

Still not solved

Please include:

• Platform and OS version of both devices
• App version
• Network environment (same Wi-Fi / guest network / VPN / proxy / corporate or hotel network)
• Whether local network permission was granted
• Whether both ends use Nearby Sync
• Reproduction steps (shortest path)

Next steps