Sebastian Scheibner
Sebastian Scheibner
This should be easy to implement. If the receiver isn't a valid phone number, the receiver could be looked up in the contact store.
Might be caused by corrupted account files, but then device linking also wouldn't work ... Which signal-cli version are you using and do you use a self-compiled libsignal-client version? Also...
Looks like sending worked successfully ... can you get logs from the other device as well? The bad key type exception originates from within libsignal-client (https://github.com/signalapp/libsignal-client/blob/600b9070c12fa0e6983c567acc0e0306a75c34c1/rust/protocol/src/curve.rs#L43). A stack trace would...
I haven't looked at the WebRTC implementation in signal yet, so I don't know if this is possible or how difficult it would be. This needs more investigation.
Would be possible. That would need some retry method in signal-cli to recheck accounts that failed to load due to a missing internet connection. At startup signal-cli needs to check...
Closed by #1259
@CarlKuhligk you seem to be running signald, not signal-cli (`io.finn.signald`) I don't know where the bad key error comes from, but you could try resetting the session. (`signal-cli send -e...
Superseded by #1259
Actually there's no workaround necessary anymore, now a link with the token is shown after solving the captcha. https://github.com/AsamK/signal-cli/wiki/Registration-with-captcha#get-captcha-token
Maybe the verbose log prints something useful `-vv`