Whisperfish - The unofficial SailfishOS Signal client

Does anyone know how to remove this notification that appears every time I log into the app?

1 Like

what version are you on?

What does Whisperfish itself report?
About Whisperfish/About

That’s just a friendly reminder to the users that there might be an update, and for us that there should be an update :sweat_smile:

If you really want to make it go away until we release the next update, you can edit MainPage.qml and push buildDate on line 13 forwards a few months.

5 Likes

Today I missed some messages in groups for which I normally get messages again. They are present in SD and Signal on Android, however.

I actually found and fixed a bug regarding group updates which should make group refresh work again. Also, handling group updates has been progressing nicely; members joining and leaving the group is now handled properly (among other but yet to be tested operations too). A long way to go still, but it’s getting there… Stay tuned!

13 Likes

One glitch in version v0.6.0-beta.34 is for me that no image attachments as well as pictures from the camera are transmitted. They show up totally blurred on the other end.

1 Like

Which was discussed here 2-3 weeks back.

1 Like

I have the same on C2 (latest OS)

Whisperfish 0.6.0-beta.35

This release contains several important fixes to basic functionality, as well as plenty of GUI fixes and performance improvements all around.

  • Fixed the issue causing some Whisperfish users getting unregistered
  • Uploading attachments works again
  • Reading expiring messages properly starts their expiration again
  • Fix refreshing groups (i.e. saving new recipients failed in some circumstances)
  • Keep muted + archived session archived when a message arrives
  • Fixes in handling and marking unregistered recipients
  • Show formatting, links, spoilers etc. correctly in main page and app cover
  • Fix broken message bubble layout in some cases
  • UI and database performance improvements
  • Don’t repeatedly print missing emoji errors

A few additional notes:

This release fixes the cause behind Signal kicking some Whisperfish users (myself included) out. If your account was removed, it requires a re-registration. This unfortunately means that, for the time being, your old messages in Whisperfish are unavailable. We are creating a message restore feature, which is released in a later update. However, the old messages in linked Signal Desktop remain accessible after re-linking. Apologies for any inconveniences.

When a message arrives (or you send a message) to a chat which is both muted and archived, it doesn’t pop back to active conversations any more. This makes it possible to have some noisy or sensitive chats to stay out of the main page, maximising the privacy aspect in that sense. This means you’ll have to check out the archived conversations in main page pulley menu manually to check the new messages. The cover page unread sessions count includes those as well, so that works as a hint.

24 Likes

Nice fixes, thanks for the release!
It bothered me way more then I’d like to admit that the app cover wasn’t formatted properly :flushed:

3 Likes

Haha that made my day, thanks for the laugh :smiley:

2 Likes

Thanks for your awesome work! I’ve removed my .local and .share directories and tried to re-register as primary device but still run into the ā€œError Failed to setup Signal clientā€ error message (I’ve tried a few times). I’m not sure if this might still be due to a missing post-quantum crypto-key or if it’s something else. Should I create a new issue on github or do you think there’s a better place (irc, existing issue)? Please let me know in what way I could help best!

1 Like

I’m unfortunately still running into this problem with the new release. You too?

I just checked if I could register with the official Signal app, and that worked, so the problem is definitely located within Whisperfish. Then I checked if I could reregister from Whisperfish after having reregistered in the official app, but that still gives the same error. But registering as a secondary device works, at least!

Meanwhile I had to switch to another primary device. I’ve tested the new release only with the secondary device registration and that works now, as you mentioned.

1 Like

A new issue is always welcome. If we spot a dupe, then it should get triaged quite quickly anyway. Don’t forget the logs, and thanks for trying! :slight_smile:

4 Likes

Same issue here now. Registration worked a few days ago, but I mistakenly set a password. Now trying to re-register without a password it fails. The only thing in the logs is this:

2025-06-09T17:08:55.238307Z ERROR run: whisperfish::worker::setup: Error in
registration: Not allowed to request verification code, reason unknown: Regi
strationSessionMetadataResponse { id: "<base64...>", next_sms:
Some(0), next_call: None, next_verification_attempt: None, allowed_to_reques
t_code: false, requested_information: [], verified: false }
1 Like

Interesting. The above was the only relevant thing in the logs for that attempt. That attempt was made after a bunch of previous failed attempts, and at that point it had stopped asking for the captcha.

I just gave it another try, and this time it asked for the captcha again. There was more stuff in the log:

[W] unknown:0 - "/home/defaultuser/.cache/be.rubdos/harbour-whisperfish/.moz
illa/ua-update.json" parse error "illegal value" at offset 0
greHome from GRE_HOME:/usr/bin
libxul.so is not found, in /usr/bin/libxul.so
Created LOG for EmbedLiteTrace
[D] onUrlChanged:120 - Url changed to: https://signalcaptchas.org/registrati
on/generate
Created LOG for EmbedLite
Created LOG for EmbedPrefs
Created LOG for EmbedLiteLayerManager
=============== Preparing offscreen rendering context ===============
[D] onUrlChanged:120 - Url changed to: https://signalcaptchas.org/registrati
on/generate
library "libandroidicu.so" needed or dlopened by "/system/lib64/libmedia.so"
is not accessible for the namespace "(default)"
[D] onRecvAsyncMessage:128 - CaptchaDone Received!
[D] onRecvAsyncMessage:128 - CaptchaDone Received!
[D] onRecvAsyncMessage:128 - CaptchaDone Received!
2025-06-10T16:00:23.368153Z DEBUG whisperfish::qtlog: qml/pages/RegisterPage
.qml:78:handleCaptcha(): Received captcha: signalcaptcha://signal-hcaptcha.<base64>
[D] :108 - Captcha code sent!
[D] onUrlChanged:120 - Url changed to:
2025-06-10T16:00:24.031517Z ERROR run: whisperfish::worker::setup: Error in
registration: Authorization failed
2025-06-10T16:00:24.031735Z DEBUG run: whisperfish::qtlog: qml/harbour-whisp
erfish-main.qml:429:expression for onClientFailed(): [FATAL] client failed
2025-06-10T16:00:24.051550Z DEBUG run: whisperfish::qtlog: qml/pages/FatalEr
rorPage.qml:25:onCompleted(): [FATAL] error occurred: Failed to setup Signal
client```