Issue is reported.
2 Likes
Suddenly when in low quality signal (on a ferry out to the sea) lost WF websocket connection. This was two days ago and connection never came back (status logo is stubbornly red on the cover).
Signal android works fine on my Xperia 10III / SFOS 4.6.0.13.
Sending/receiving messages via WF not possible (well, obvious because no connection to wesocket).
Booting 10x has not helped.
How can I investigate?
Does it help if I try the fault finding via settings? (Settings page itself is triggering a lot of crashes now)
That sounds like an awful lot like the PNI issue. If youâre familiar with using terminal - either on-device or via ssh - you could try to launch Whisperfish using this command:
devel-su -p harbour-whisperfish --verbose
If you get an error message something like Error(Char { character: 'P', index: 1 }) that is the issue.
Actually, to everyone else too, the major PNI implementation work is now finally done and merged, and weâre approaching a new release! The latest Whisperfish release doesnât contain the fix, but we know first hand the urgent need of it.
There has been a lot of other development too, so stay tuned!
8 Likes
Hello, thanks for the instructions, here are the parts I assume are the important bits:
2024-08-25T04:10:05.904175Z INFO whisperfish::worker::c
lient: Received receipt: 1724332812577
thread âmainâ panicked at /home/mersdk/cargo/git/checkou
ts/libsignal-service-rs-e91a0c40cab55da9/93c23cf/libsign
al-service/src/envelope.rs:143:14:
valid uuid checked in constructor: Error(Char { characte
r: âPâ, index: 1 })
stack backtrace:
0: 0x5de3706380 -
1: 0x5de320fdb0 -
2: 0x5de3702238 -
3: 0x5de37061b4 -
2024-08-25T04:10:05.910326Z ERROR set up message receive
r:websocket: libsignal_service::websocket: SignalWebSock
et: Websocket error: request handler failed
2024-08-25T04:10:05.913103Z INFO libsignal_service_hype
r::websocket: Websocket sink has closed: SendError { kin
d: Disconnected }.
I can send whole verbose as PM if needed.
Nice to hear that a new version is coming again 
Thanks for the log snippet. That is the PNI issue indeed, so itâs fixed already 
We just need to get a new release out⌠Thereâs no need for the full log.
3 Likes
PSA: messages sent from Whisperfish with one or more attachments are silently ignored on iOS clients. That includes voice notes.
Weâll try to get this fixed asap⌠and weâll try to get a PNI release out soon too! 
8 Likes
Hello, i tried to use Whisperfish: installed v0.6.0-beta.28 using Storeman on SailfishOS 4.6.0.13. Used a different phone with the iOS version of signal running to send some messages. Registration seems to work, the other phone finds the one with whisperfish installed i want to use, but no message is displayed. When i debug i get the âcharacter P, index 1â error described above. Looks to me like i cannot use this version. Should i install an older version instead? Or wait for the next release?
No hurry, i really appreciate the work you are doing.
Regards, Bruno
Hold off for the next release. Itâs been fixed on master for a while, but there are a few other issues that we want to iron out before releasing
Never downgrade Whisperfish, that has never been a solution and only makes things worse.
1 Like
This release does not fix registration nor linking yet! Itâs a bit more work than anticipated, so Iâm getting this one out already.
Whisperfish 0.6.0-beta.29
(Mostly, finally) implement PNI, thanks to @direc85
Should fix many crashes
Changes
- Implements PNI endpoint receiving, PNI-sent endpoint receiving
- Performance improvement for blurhash rendering
- Empty GV2 update message fixes
- libsignal bump
- Use Speech Note automatic model instead of English
14 Likes
I cannot setup Whisperfish 0.60.beta29.0 on either Xperia 10 iii and Xperia 10 V under OS 4.6.0.15 as linked device. An error message appears after scanning the QR code and the suggestion to restart Whisperfish. This error reproduces consistantly after re-install and deleting the config files in home directories. What am I doing wrong? Shall I provide some logs? If so, where to fibd these?
1 Like
@MeeGo-Junky beta 29 doesnât allow for registration or linking; youâll have to wait for a version that includes this patch to be released.
Hopefully we can fix this during the hackathon this weekend!
7 Likes
Ah cool, I somehow missed this piece of information, thanks
1 Like
PSA: Changing the message expiry timer for groups is currently broken in Whisperfish. Setting the timer causes the group chat to not render at all, until another message has been sent.
Setting the expiry for direct messages has also changed lately, but luckily it currently works.
Weâre working on an fixing/mitigating this as I type this, but in the meantime, please use Signal Desktop to change the expiry messages timeout if possible, and avoid changing the group message expiry timers in Whisperfish.
3 Likes
Just a little progress update: The fixes needed to make linking a Signal Desktop (and linking Whisperfish to Signal Android or another Whisperfish as well) are now merged. It is still essential to have a linked Signal Desktop with a primary-registered Whisperfish, and now that is again possible to achieve. Luckily any previously linked SDâs worked fine (but complained under the hood a lot).
A lot of that happened during the Sailathon event, but the work was completed just after it. A big thanks to everyone involved!
There are a few nasty bugses Iâd still like to squash before the next release, so please donât hold your breath just yet. It should happen Soon⢠however so, as always, stay tuned!
17 Likes
hi there,
lost my first device (was the android app in waydroid), then lost the desktop-app due to some keystore issue.
whisperfish is now my sole installation.
is there a way to âbackupâ, extract enough personal data to be able to reuse it for seting up a new android app ?
i know i do ask too late, but still âŚ
I think, to truly regain control over your account, you need access to your primary device. From your post, I infer itâs the Android app in Waydroid, and not Whisperfish. We currently donât have the backup functions built-in, and I donât expect to build them any time soon either⌠itâll be a lot of work.
So, sorry, but I donât think we can help you out here 
2 Likes
If youâve used the backup feature of the original Android app, you can use it and itâs encryption key to restore a new installation and with that, relink Whisperfish and the desktop application.
Also if youâve still got access to the âcorruptedâ Signal desktop application files, either through backups or simply because youâve not deleted them or overwritten them with a clean installation yet, you can also quite easily get that to work again by reinstalling Signal desktop by a newer build that doesnât have that issue, and restoring the right files and directories from before the keystore issue.
It will want to be relinked to a phone app, but youâll have all history and files from your initial desktop app setup point to the keystore corruption point.
Apologies for offtopic 
3 Likes
I donât see how thatâs off-topic
1 Like
Hi does Whisperfish send attachments properly?
i am on beta 29.
yesterday all was fine.
Today no attachments will send.
In Terminal i can see followed errors :
2024-10-22T14:14:48.123860Z ERROR w
hisperfish::worker::client: Sending
message: Failed to upload attachme
nt: Not found.
2024-10-22T14:14:48.124088Z ERROR l
ibsignal_service::websocket: Signal
WebSocket: Websocket error: SignalW
ebSocket: end of application reques
t stream; socket closing
But this is not correct i picked the photo from gallery 
Nope. Beta 30 will fix this, and will fix the iOS sending. Attachment sending fails since yesterday or today! Iâll try to find some time to finalize b30 tomorrow. @direc85, if you have the chance, could you send your wishlist over? 
3 Likes