Windows 10 client cannot be found under 'Nearby devices' about localsend

[Caesarovich]

Hi @wadid , thanks for opening this issue. If you changed the port on one of your devices, you need to change it as well on all the other devices you want to share files with. We are aware that it is quite inconvenient and are working on a better streamlined solution.

Could you try this and comeback with a reply if it succeeded/failed ?

[Robio]

I'm having the same problem. Same configuration: Mac/Android/Win10. Win10 installation does not appear to other devices, and vice versa. All devices have matching ports.

LocalSend v1.14.0 (45) on Windows.

[Caesarovich]

Hi,

Can you try using the Autofix functionality?

You can find it under Send > Troubleshoot > Fix automatically.

[Robio]

Can you try using the Autofix functionality?

You can find it under Send > Troubleshoot > Fix automatically.

Tried that. No effect. Although I'm not sure what was supposed to happen. Clicking [Fix Automatically] launched cmd.exe, which populated with...

Ok.
Ok.
Press any key to continue . . .

I pressed [Enter], and cmd.exe closed.

• All my devices are on the same wi-fi (I even checked that the are all on the 5.0GHz band of the network)

• Mac, iPhone, and 2 Android phones can find, send and receive

• Win10 & Chromebook can't find any other devices

• Chromebook does appear on other devices, but Win10 does not

• On Win10 > Windows Defender Firewall, I found 2 inbound rules for LocalSend that were blocked

• I allowed them

• Didn't help

• Figured out how to make a rule in Defender for LocalSend on port 53317
  ✓ That worked

Any idea why these extra steps were required? I don't have any special security settings on this device.

Also, any suggestions for fixing this problem on the Chromebook?

Thanks!

[Robio]

@Caesarovich re-replying with the last question from my previous comment:

Any idea why these extra steps were required? I don't have any special security settings on this device.

Also, any suggestions for fixing this problem on the Chromebook?

[Caesarovich]

Hi @Robio , I am not too familiar with the way the Windows Defender interacts with the Windows firewall. The Fix automatically button creates "allow inbound" rules in the Windows firewall. It is usually sufficient to fix the firewall issues if such rules were not created at install. So I don't really know what happened in your case for you have to manually edit the firewall rules.

For your Chromebook I have no idea as well as to my understanding Chromebooks cannot install any application. We have a fair number of Chromebooks at my workplace and these only contain the Chrome browser. So I am really curious to know how you managed to install LocalSend on it.

But if LocalSend doesn't work properly on your Chromebook even after successfully installing it; I don't think we can help you as Flutter (and thus LocalSend) doesn't have any support for ChromeOS. Furthermore LocalSend relies on libraries and APIs that are specific to the Windows/Linux/android/apple platforms and which might not exist on Chrome OS.

I'm sorry to not be able to help you further on these issues.

[Robio]

@Caesarovich , Chromebooks can install most Android apps, as Chrome OS is, for the most part, a bastardized Android OS. They come with the Play Store pre-installed and everything. How well they run is a different matter, since most developers are developing with phones and tablets in mind.

Our household Chromebook is running — successfully for the most part — Aqua Mail, UpNote, Enpass, Simplenote, Twitch, GSAM, Comixology, Floating Notes, Spotify, and others. Perhaps your workplace Chromebooks are deliberately crippled by IT. :)

I'd love to see LocalSend work on Chromebook, but until that glorious day, we'll limp along using Google Drive. :)

Thanks for the detailed reply.

[wadid]

This worked for me actually. Both devices same port. But I needed some tries to find a free port. 65000 seemed to work for me.

[Mujtaba0150]

This worked for me actually. Both devices same port. But I needed some tries to find a free port. 65000 seemed to work for me.

The issue you were experiencing was most likely due to the fact that the port range above 49152 is for dynamically allocated ports, which can cause issues when it comes to apps like Localsend which expect a hardcoded port on both ends. Its best to use a range between 1024 to 49151 because these are not dynamic ports and don't require privilege escalation