Crashed when first opened about siggo HOT 7 CLOSED

I set save_messages to true before opening it for the first time, could that be it? After setting it to false it no longer crashes.

from siggo.

Hey, thanks for the report! I will take a look at this.

from siggo.

After it ran successfully, did you turn message saving back on?

from siggo.

I went to try and test this, but then it crashed again with the exact same stack trace. save_messages was false this time. I opened it, a message came in and was displayed, and then it crashed right away.

from siggo.

Hey @makeworld-the-better-one, sorry to hear. I'll take a look when I get a chance. I haven't tested it yet with signal-cli 0.7, and I fear that may be the cause of some of these issues. I have only ever used siggo with signal-cli 0.6.

Also, thanks so much for telling me about cview.

I started a new job in December and I haven't had as much time to hack on this project in the past 2 months, but I will try and look into this as soon as I can.

from siggo.

Oh yeah, I'm using the latest signal-cli 0.7.4.

Also, thanks so much for telling me about cview.

You're welcome, good luck with it! It's great.

And no worries. Thanks for getting back to me.

from siggo.

i've also been trying to get siggo running with 0.7.4. I have a patch that seems to work for me: https://gist.github.com/kverb/8541f95287dcd886f638406af36257b3 [edit: this only fixes individual chats; not sending in groups]

it seems there are two main issues that are affecting this and #29 :

1. siggo is crashing on trying to load groups from signal-cli's data file. I believe this is caused by the SignalGroup structs' members type. Changing to a simple string list seems to fix it.
2. siggo appears to be doing nothing when running. This is observable if you enable the log and see that it just continually loops on starting dubs daemon... scanning stdout. Perhaps this is due to a new warning that signal-cli emits upon launching in daemon mode : WARN DaemonCommand - "--json" option has been deprecated, please use the global "--output=json" instead.

I'm not going to submit a PR, but please feel free to take a look at my patch changes.

from siggo.