Yep, right around 8pm for me, if I had to pin it down.
1 Like
Same here. I can receive messages, but when I try to send one, I donāt get the empty message any more, and an HTTP status code 500 on the terminal. It could be that something has changed on the server sideā¦
Same problem here, everything worked fine until about Friday evening (Jolla Phone, SailfishOS 3.4.0.24, Whisperfis v0.6.0-beta.1). Same status code, unexpected response 500. I can receive messages but none of mine arrive at any recipient.
There is an issue for it already. Please give it a thumbs up so it gets tackled sooner.
2 Likes
Hi folks, seems like literally everyone is affected, and that includes myself (hooray!). Iāll fix it right after breakfast tomorrow. If itās an easy fix, Iāll make sure to push beta.2 then. 
7 Likes
So ehh, Iāve been reading server code. Signal has been fixing a bunch of NPEās.
I have a question for the Whisperfish user community: is there anyone for whom sending messages does still work? Especially those who had the 500 errors before: did they reappear, or stay away?
Paper trail post: still 500, and I will keep trying on and off.
āIt has been loggedā is hopefully something OWS will react to, and/or the details of a fix (and/or workaround) will pop up here and/or on irc and/or on matrix soon.
Thanks for checking in on this!
For me the 500 errors came back as well.
Me neither, no messages get delivered.
Canāt tell about the 500 error, sorry.
edit: ā¦and no messages come in.
1 Like
I canāt send messages, too. Desktop client works as a workaround.
Currently, cannot send or receive any message. Last message received around April 20th.
Thatās strange; messages coming in still works for me (and all others that I talked to)
1 Like
Got it. Itās both a server-side as well as a Whisperfish-side bug. Short explanation: Signal used to use (and still does use) the X-Signal-Agent header instead of User-Agent. The new Signal rate limiting logic however requires User-Agent to be set, which we didnāt set at all, and as such causes a null pointer exception at server side. I still donāt see exactly where this is caused, but setting User Agent (to an honest Whisperfish/0.6.0-beta.2, by the way) fixes the issue.
This means that Iām pushing beta.2 now. Iāll have a 
on my balcony while the CI draws the rest of the 
. The new version should appear automatically on OpenRepos later tonight. If it doesnāt, Iāll push manually in two hours.
Whisperfish 0.6.0-beta.2
Emergency release for the HTTP-500 ānothing can be sendā bug.
Features
-
My Backup compatibility (thanks to Nthn).
- You need to reset all sessions manually after a reset, if they had been touched after taking the backup.
-
Share to Whisperfish functionality (thanks to Gabriel Margiani)
- Enabling on SailfishOS 4.0 needs some additional work.
- Database VACUUM option in settings (thanks to Igor Makarov)
- Initial work to decouple Whisperfish from SailfishOS (thanks to Be)
- Migrated to libsignal-client.
Fixes
- The infamous āI canāt send anything anymoreā HTTP-500 issue
- Crash on certain session resets
9 Likes
Thanks for the fast response to this issue!
I just installed the beta.2 from gitlab, but now I get a new error message:
Error sending message: Protocol error: bad key type <0x2e>
anyone else having this issue?
Yes, @mjtorn had that too: Weird key issues on the master branch (#354) Ā· Issues Ā· Whisperfish / Whisperfish - Signal on Sailfish OS Ā· GitLab, and as such I didnāt upload let it be uploaded to Openrepos yet. Looks like Iāll have to investigate that first.
1 Like
@raumzeit, because of that problem I didnāt upload beta.2. Iāve tried some stuff this morning, and got multiple people to say that they donāt get the bad key errors any more. Therefore, beta.3 is now on Openrepos.
Whisperfish 0.6.0-beta.3
Emergency release for the HTTP-500 ānothing can be sendā bug and the BadKeyType bug.
Fixes
- Identity key read errors
- Update local storage format quirks for future Signal versions
If this thing seems to stay a bit stable, the next version is going to be called 0.6.0, for real, and then Iāll finally start semverring again 
11 Likes
Thank you so much!
Sending messages works like a charm again.
Iām very much looking forward to the upcoming 0.6.0 release, and all the other future goodies to come. Maybe at some point I can also contribute, but I mostly code in C and have no experience whatsoever with Rust or QMLā¦
Cheers!
1 Like
sending works again ā¦
thanks !!
1 Like
great it is working again
1 Like
Feel free to come and have a chat on #whisperfish:rubdos.be or #whisperfish:libera.chat. Contributing will soon become easier, now that I can finally build Whisperfish in the standard SailfishOS SDK
5 Likes