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
Soduto will stay connected to my phone for a few seconds after I close the lid of my MacBook and after sometime it will disconnect. But when I open the lid back up, Soduto doesn't automatically connect to my phone. I have to tap on the Menu bar icon once for it to check for nearby devices and connect to my phone. Is this a bug?
EDIT: I'm not sure if this is the right way as I'm a noob when it comes to Swift, but after I added a didWakeNotification listener in AppDelegate and executing self.statusBarMenuController.refreshDeviceLists() when it receives the wakeup notification, it seems to have fixed the issue. If there is a better approach than this, please feel free to share.
The text was updated successfully, but these errors were encountered:
I couldn't reproduce the issue. It seems soduto only listening on the socket, the phone (kde connect) that initiate the connection. Are you sure kde connect still running and not killed? try exclude it from battery saver feature on the phone.
It's ok, I'm also new to Swift, my main goal of this fork just to get working native build for my m1 mac. Feel free to open pull request.
Soduto will stay connected to my phone for a few seconds after I close the lid of my MacBook and after sometime it will disconnect. But when I open the lid back up, Soduto doesn't automatically connect to my phone. I have to tap on the Menu bar icon once for it to check for nearby devices and connect to my phone. Is this a bug?
EDIT: I'm not sure if this is the right way as I'm a noob when it comes to Swift, but after I added a didWakeNotification listener in AppDelegate and executing self.statusBarMenuController.refreshDeviceLists() when it receives the wakeup notification, it seems to have fixed the issue. If there is a better approach than this, please feel free to share.
The text was updated successfully, but these errors were encountered: