You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if connected to a device, then you can give it a name that is used remotely.
But the global name isn't defined, what results in syncthing (web) displaying the ID instead on prompts - while some frontends (i.e. the other android one) show errors.
So the other android-client displays notifications like "Syncthing Device null want's to share Directory foobar"
The text was updated successfully, but these errors were encountered:
I'll add a non-null default. Could you tell me more about your test device, and (if you know) the protocol messages where the device name field is null?
Well, the device i tested on was a Nexus 6p with googles current Android 7.1.1 Beta build
As for protocol messages - i don't have those and i just deinstalled your tool
Further: model-name sounds like a bad Idea to me. My wife and i both had the same phone, as do my parents. I find it plausible that people would want to connect multiple similar devices.
if connected to a device, then you can give it a name that is used remotely.
But the global name isn't defined, what results in syncthing (web) displaying the ID instead on prompts - while some frontends (i.e. the other android one) show errors.
So the other android-client displays notifications like "Syncthing Device null want's to share Directory foobar"
The text was updated successfully, but these errors were encountered: