flare-signal: document linking/registration issue
This commit is contained in:
parent
29cde5e724
commit
f129afdae8
|
@ -1,15 +1,18 @@
|
||||||
# Flare is a 3rd-party GTK4 Signal app.
|
# Flare is a 3rd-party GTK4 Signal app.
|
||||||
# UI is effectively a clone of Fractal.
|
# UI is effectively a clone of Fractal.
|
||||||
#
|
#
|
||||||
# compatibility:
|
### compatibility:
|
||||||
# - desko: works fine. pairs, and exchanges contact list (but not message history) with the paired device. exchanges future messages fine.
|
# - desko: works fine. pairs, and exchanges contact list (but not message history) with the paired device. exchanges future messages fine.
|
||||||
# - moby (cross compiled flare-signal-nixified): nope. it pairs, but can only *receive* messages and never *send* them.
|
# - moby (cross compiled flare-signal-nixified): nope. it pairs, but can only *receive* messages and never *send* them.
|
||||||
# - even `rsync`ing the data and keyrings from desko -> moby, still fails in that same manner.
|
# - even `rsync`ing the data and keyrings from desko -> moby, still fails in that same manner.
|
||||||
# - console shows error messages. quite possibly an endianness mismatch somewhere
|
# - console shows error messages. quite possibly an endianness mismatch somewhere
|
||||||
# - moby (partially-emulated flare-signal): works! pairs and can send/receive messages, same as desko.
|
# - moby (partially-emulated flare-signal): works! pairs and can send/receive messages, same as desko.
|
||||||
#
|
#
|
||||||
# error signatures (to reset, run `sane-wipe flare`):
|
### debugging:
|
||||||
# - upon sending a message, the other side receives it, but Signal desktop gets "A message from Colin could not be delivered" and the local CLI shows:
|
# - `RUST_LOG=flare=trace flare`
|
||||||
|
#
|
||||||
|
### error signatures (to reset, run `sane-wipe flare`):
|
||||||
|
#### upon sending a message, the other side receives it, but Signal desktop gets "A message from Colin could not be delivered" and the local CLI shows:
|
||||||
# ```
|
# ```
|
||||||
# ERROR libsignal_service::websocket] SignalWebSocket: Websocket error: SignalWebSocket: end of application request stream; socket closing
|
# ERROR libsignal_service::websocket] SignalWebSocket: Websocket error: SignalWebSocket: end of application request stream; socket closing
|
||||||
# ERROR presage::manager] Error opening envelope: ProtobufDecodeError(DecodeError { description: "invalid tag value: 0", stack: [("Content", "data_message")] }), message will be skipped!
|
# ERROR presage::manager] Error opening envelope: ProtobufDecodeError(DecodeError { description: "invalid tag value: 0", stack: [("Content", "data_message")] }), message will be skipped!
|
||||||
|
@ -18,7 +21,8 @@
|
||||||
# - this occurs on moby, desko, `flare-signal` and `flare-signal-nixified`
|
# - this occurs on moby, desko, `flare-signal` and `flare-signal-nixified`
|
||||||
# - the Websocket error seems to be unrelated, occurs during normal/good operation
|
# - the Websocket error seems to be unrelated, occurs during normal/good operation
|
||||||
# - related issues: <https://github.com/whisperfish/presage/issues/152>
|
# - related issues: <https://github.com/whisperfish/presage/issues/152>
|
||||||
# error when sending from Flare to other Flare device:
|
#
|
||||||
|
#### error when sending from Flare to other Flare device:
|
||||||
# - ```
|
# - ```
|
||||||
# ERROR libsignal_protocol::session_cipher] Message from <UUID>.3 failed to decrypt; sender ratchet public key <key> message counter 1
|
# ERROR libsignal_protocol::session_cipher] Message from <UUID>.3 failed to decrypt; sender ratchet public key <key> message counter 1
|
||||||
# No current session
|
# No current session
|
||||||
|
@ -26,6 +30,32 @@
|
||||||
# ```
|
# ```
|
||||||
# - but signal iOS will still read it.
|
# - but signal iOS will still read it.
|
||||||
#
|
#
|
||||||
|
#### HTTP 405 when linking flare to iOS signal:
|
||||||
|
# [DEBUG libsignal_service_hyper::push_service] HTTP request PUT https://chat.signal.org/v1/devices/{uuid}.{timestamp?}:{b64-string}
|
||||||
|
# [TRACE libsignal_service_hyper::push_service] Unhandled response 405 with body: {"code":405,"message":"HTTP 405 Method Not Allowed"}
|
||||||
|
# [ERROR flare::gui::error_dialog] ErrorDialog displaying error: Something unexpected happened with the signal backend. Please retry later.
|
||||||
|
# [TRACE flare::gui::error_dialog] ErrorDialog full error: Presage(
|
||||||
|
# ProvisioningError(
|
||||||
|
# ServiceError(
|
||||||
|
# UnhandledResponseCode {
|
||||||
|
# http_code: 405,
|
||||||
|
# },
|
||||||
|
# ),
|
||||||
|
# ),
|
||||||
|
# )
|
||||||
|
# flare matrix suggests the signal endpoint has changed:
|
||||||
|
# - "/v1/device/link instead of confirming via /v1/devices/{I'd}"
|
||||||
|
# - this endpoint is declared in libsignal-service-rs (used both by flare and presage)
|
||||||
|
# - libsignal-service/src/provisioning/manager.rs
|
||||||
|
# - libsignal-service issues a put_json to that URL (i.e. HTTP PUT)
|
||||||
|
# - libsignal-service is "based on" the official rust signal API <https://github.com/signalapp/libsignal>
|
||||||
|
# - did these guys recently change it?
|
||||||
|
# - no, but Signal-Desktop did. see ccb5eb0dd2 from 2023/08/29
|
||||||
|
# - that's a fairly involved change.
|
||||||
|
# - signalcli is reporting this same error: <https://github.com/AsamK/signal-cli/issues/1399>
|
||||||
|
# - Mixin Messenger / libsignal_protocol_dart doesn't seem to be reporting any issue
|
||||||
|
# - <https://github.com/MixinNetwork/flutter-app>
|
||||||
|
#
|
||||||
# well, seems to have unpredictable errors particularly when being used on multiple devices.
|
# well, seems to have unpredictable errors particularly when being used on multiple devices.
|
||||||
# desktop _seems_ more reliable than on mobile, but not confident.
|
# desktop _seems_ more reliable than on mobile, but not confident.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue
Block a user