Whisperfish - The unofficial SailfishOS Signal client

Hi, don’t know if this issue is an issue. Sent messages from my primary device (iphone) are not synchronized with the linked whisperfish device. Incoming messages are synchronized.
My feeling is, that this worked before.
Cheers Alex
Recent WF version

1 Like

I’ve seen similar behaviour recently, and I’m really not sure what’s going on for the moment. Keeping an eye on it.

1 Like

Hey @alex0008, is this happening in a specific session, or is this for all messages in groups and direct messages from your iPhone?

If it’s on a specific session: has that session ever been used with disappearing messages? Feel free to send me a DM if that’s easier for you.

1 Like

c.f. SMS received time displayed has false timezone adjustment

Possibly the same category of issue, but the code paths are extremely far apart. The core issue is, in my opinion, that most Sailfish OS developers are somewhere around UTC, and so we don’t really notice TZ issues all that easily.

Since today I cannot reach my contacts anymore. There is one hook and the recipient doesn’t get the message.

Does that happen for all contacts, or just a single one? Would be good to have logs for both sending a message and for receiving a message.

Happened for all my contacts. I used Signal for yesterday and rebooted my phone some minutes ago, now the problem is gone. Strange…

1 Like

Interesting. Sounds like somehow the unidentified socket didn’t want to connect for you. We’re completely rewiring that logic in the next release (and we’ve been ironing out bugs for months now…), so hopefully that won’t have to happen again.

10 Likes
Good evening, on the phone of my wive we must do a factory reset. 
Badly i forgot to save, the config / identity from whisperfish. 

So we tried to register with last whisperfish version from openrepos also the last version from gitlab. 

Every Time the registering fails with : Einrichtung des Signalclients fehlgeschlagen

We tried ca. 5 times with waiting 1 till 2 days.
Also i cleaned before a new try :

rm -rf ~/.local/share/harbour-whisperfish ~/.config/harbour-whisperfish ~/.local/share/be.rubdos/harbour-whisperfish ~/.config/be.rubdos/harbour-whisperfish

My wive never made a account with official sinal or molly app so i think it is not the problem described: 

"Wait for seven days (don't use your other Signal client); or
Disable "registration lock" in the settings of Signal Android/Signal iOS."

this evening i tried again and now i started whisperfish from terminal 
Everything works fine captcha is okay we got SMS code
Then after filling out the pin the error belows shown :(
i deleted some code... 

[D] onRecvAsyncMessage:128 - CaptchaDone Received!
[D] onRecvAsyncMessage:128 - CaptchaDone Received!
[D] :108 - Captcha code sent!
[D] onUrlChanged:120 - Url changed to: 
2026-05-19T18:57:29.495744Z  INFO whisperfish_store::store: Creating directory structure
2026-05-19T18:57:30.241816Z ERROR run: whisperfish::worker::setup: Error in registration: Service error: Unexpected response: HTTP 422




Aye, client registration appears to be broken right now. I installed Whisperfish Beta.40 via Storeman, started it, set a password, gave it my number, opted to use as primary device, passed the captcha, got the text message with the OTP, entered said otp and got an error:

Same error appears after restarting and even un- and reinstalling Whisperfish, and I can’t do anything but close the app again at this point.

This is what it says on the command line when the error occurs:

2026-05-23T11:55:53.196641Z ERROR run: whisperfish::worker::setup: ACI UUID not set after registration or opening storage! 
2026-05-23T11:55:53.198043Z DEBUG run: whisperfish::qtlog: qml/harbour-whisperfish-main.qml:431:expression for onClientFailed(): \[FATAL\] client failed
2026-05-23T11:55:53.230666Z DEBUG run: whisperfish::qtlog: qml/pages/

Well, there’s good news and bad news regarding registration. @Neuntausend and @monkeyisland are probably facing the same issue.

The bad news is there were indeed a bunch of protocol changes. The good news is we already have most of it implemented, but notably registration and linking is still missing!

10 Likes

I recently tried to install Whisperfish for the first time and ran into a similar issue as @Neuntausend, however I didn’t get past the captcha or receive a SMS message.

Looking forward to giving it a try though!

1 Like

I managed to get the WebSockets branch working today with the latest refactors, so it’s a lot closer to merge now. It has been bottle-necking us for quite some time now, but we should be able to finally progress with other issues (e.g. registration) soon.

20 Likes

Stunning work, thank you so much for the work you put for WF❤

5 Likes

Voicenotes i Whisperfish are broken in SFOS 5.1.0.8 (early access). Recording is counting time, but the resulting Voicenote is not playable.

1 Like

Whisperfish works for me in 5.1.0.8.

1 Like

Has been fixed and merged yesterday upstream by @direc85. Next release will fix that!

12 Likes

HI there - X10 III on SFOS 5.1.0.8
I recently wanted to link an external device to WF and realised that it wasn’t connected.
I was able to get this via journal log

Jun 03 18:45:33 Xperia10III harbour-whisperfish[5511]: Error starting stream: Websocket error: websocket upgrade failed
Jun 03 18:45:33 Xperia10III harbour-whisperfish[5511]: Retrying in 10
Jun 03 18:45:33 Xperia10III harbour-whisperfish[5511]: Error starting stream: Websocket error: websocket upgrade failed
Jun 03 18:45:33 Xperia10III harbour-whisperfish[5511]: Retrying in 10
Jun 03 18:45:34 Xperia10III harbour-whisperfish[5511]: Not connected to server, cannot initialize PNI. Retrying in 10 seconds.

Rebooted, tried a few things. Ideas?

You’ll have to reset that Whisperfish installation; it seems like that whole instance was unregistered. However, registration and linking is currently broken. We aim to fix that by next release, so there’s nothing you can currently do.

5 Likes