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
Hi, thanks for an awesome piece of software. I raise this issue knowing full well what a nightmare it must be to follow upstream changes here. :)
I was running 0.6.0 (cargo) on my laptop a couple of weeks ago, and after the initial device linking and restarting the application, all my contacts showed up.
I have now installed 0.6.1 (again, using cargo) on a second machine, and I cannot get contacts to show up until they send me a message.
Is this a result of #350 (and #349)? Is there anything I can do about this myself?
(Platforms: FreeBSD 14.2 and 15-CURRENT)
The text was updated successfully, but these errors were encountered:
I had to update presage real fast, and did not have time to adjust to their new API. Contacts are now sent via the output of the messages method (there is an enum there). I did not check how actually to trigger contact there. But technically, if there is still a trigger, it should be possible to restore the code removed in #350, call the trigger and handle the one enum case returned from messages.
Still the same (i think) in 0.6.2. I just linked gurk up, and contacts are all uuids, name appears for a contact when a msg is received from it. Thank you for your great work!
Hi, thanks for an awesome piece of software. I raise this issue knowing full well what a nightmare it must be to follow upstream changes here. :)
I was running 0.6.0 (cargo) on my laptop a couple of weeks ago, and after the initial device linking and restarting the application, all my contacts showed up.
I have now installed 0.6.1 (again, using cargo) on a second machine, and I cannot get contacts to show up until they send me a message.
Is this a result of #350 (and #349)? Is there anything I can do about this myself?
(Platforms: FreeBSD 14.2 and 15-CURRENT)
The text was updated successfully, but these errors were encountered: