-
Notifications
You must be signed in to change notification settings - Fork 88
discoverNetworkServices not finding any, if left idle for 1-2 minutes #26
Comments
solved by moving manger.discoverServices(.. into a Handler run every 5sec the problem is both devices must making descovery method at the same time n order to connect to each other |
That's odd since |
it's still unreliable sometimes on diveces rinning marshmillo it would't connect without recreating the client activity should I recreate Salut instance onFail of something |
aha I just saw |
another note that device.instanceName of discovered device print same as device.readableName |
Yup, try recreating the Salut instance. And yes, mac addresses have a hand in establishing a connection. Mac addresses are how the devices connect when not in a group. I didn't know that the API changed in Marshmallow. As for the second issue, I've found the line. Thanks! |
Everything works fine in all cases but not
when ClientApp starts and the HostApp starts after it by more than 1-2 minutes
-if it starts immediately it works fine-
despite ClientApp is still discovering i added a handler ever x seconds to check if isDiscovering and it is true but its like the service"device" wont be found, may be the services list is not refreshing please help with this
The text was updated successfully, but these errors were encountered: