Sebastian Scheibner
Sebastian Scheibner
Crashing in libsignal-client: https://github.com/signalapp/libsignal/blob/main/rust/bridge/jni/impl/src/logging.rs#L166
Indeed group endorsements are still on my todo list, as I don't know yet what they are exactly. They will have to be saved in the database somehow, probably similar...
I think it's caused by retrieving lots of messages. Need to check, maybe profile retrievals can be limited in signal-cli when receiving messages.
sqlite does support multiple read connections at the same time, though every write will block the database. Setting the pool size to 1 will prevent any parallel read connections. IMMEDIATE...
If this gets implemented, I'd probably go the same route as Signal-Desktop. I.e. store one master key in the keyring and use that to encrypt all other sensitive data in...
Looks like a mismatch between the java and jni (native .so file) part of libsignal-client. Both need to match the one required for your signal-cli version. https://github.com/AsamK/signal-cli/blob/master/CHANGELOG.md
signal-cli is using base64 for all binary data. I'm not a fan of adding an additional encoding scheme, as base58 conversion should be straight forward for signal-cli users.
What do you get if you run `signal-cli -a +316NUMBER getUserStatus +234NUMBER`
`getUserStatus` always queries the Signal server for the latest uuid, so it shouldn't return an old one.
Which signal-cli version are you using?