Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • Whisperfish - Signal on Sailfish OS Whisperfish - Signal on Sailfish OS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 231
    • Issues 231
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Whisperfish
  • Whisperfish - Signal on Sailfish OSWhisperfish - Signal on Sailfish OS
  • Issues
  • #354
Closed
Open
Created May 09, 2021 by Markus Törnqvist@mjtornDeveloper

Weird key issues on the master branch

Setup

  • Device: Xperia X 10 Plus
  • SailfishOS version: 4.0.1.48
  • Whisperfish version: 0b89b94a and 609843a3

Summary

This is unscientific because I didn't even think to look at the logs when I first tested commit 0b89b94a but when messages didn't seem to go through, I found errors in the logs, which were present also with commit 609843a3.

Downgrading to dc4c2b3f seems to work fine and I don't think I missed out on messages permanently, but my sent messages apparently didn't get anywhere.

Trace log

Quoting off what I pasted on IRC. Can't verify the commits for the logs further below which is which

0b89b94a

STUB requested peer identity for Recipient { id: 1, e164: Some("NUMBER"), ...}
...
ERROR harbour_whisperfish::worker::client] Error opening envelope: SignalProtocolError(BadKeyType(137))

$ grep ERROR log/fluistervis-2021-05-08T15\:09\:32  | grep -v 'Already found a session' | wc -l
22

$ grep ERROR log/fluistervis-2021-05-08T15\:09\:32  | grep -v 'Already found a session' | grep SignalProtocolError | wc -l
8

$ grep ERROR log/fluistervis-2021-05-08T15\:09\:32  | grep -v 'Already found a session' | grep 'Protocol error' | wc -l
11

the next file has only two SignalProtocolError(BadKeyType(137)) which may have been tests sent by me (hard to tell because of this uuid-type crap, plaintext would be easier to debug ;)) then four (4) 'bad key type' errors, 0x80, 0x61 and two 0x89


Grep for ERROR

[2021-05-08T16:19:30Z ERROR harbour_whisperfish::worker::client] Error sending message: Protocol error: internal error: Unknown error
[2021-05-08T16:19:32Z ERROR harbour_whisperfish::worker::client] Error sending message: Protocol error: internal error: Unknown error
[2021-05-08T16:19:44Z ERROR harbour_whisperfish::model::message] Message not found
[2021-05-08T16:19:44Z ERROR harbour_whisperfish::model::message] Message not found

so I sent a message to a group, "Test" was the content, its id 75704, and a while later I get this in the logs ServiceAddress(SISTERS_NUMBER) received a message. -> Called fetch_message_by_id(75704) -> Message not found

may also be interesting that this sister's number is one of the "issue #336" numbers I get complaints about when starting WF

Assignee
Assign to
Time tracking