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
1 Like