I haven’t had any issues with Whisperfish not delivering messages… Then again, my message frequency is so low, maybe 10-20 messages per day, that flooding can’t be it for me 
I don’t think my “opinion” matters a lot here… Expect that WF works for me (apparently I am running openrepos beta 1 after the SFOS 4.1.0 EA update, should have remembered it gets automatically downgraded to repo version) here in Finland…
1 Like
Sounds okay for me. The message that I tried to send was on Friday. I hadn’t sent a message in a few weeks, I am not that much of a chatter 
The rate limiter might be not about me, but a prekey sounds reasonable.
Too long quiet time perhaps? Some sort of timeout or expiration could be the issue…
I assume restarting the phone to fully restart tge WF and whatnot has been done?
Yeh, the fact that it’s suddenly a handful of people that get affected worries me; especially since it sounds like a server-side bug rather than a working rate limiter. Let me clarify that a bit: I think that they added the rate limiter, and that there’s a bug in their code, rather than that the rate limiter tries to rate limit us!
@direc85 Good question It was restarted (and updated) Wednesday.
For good measure I restarted it now twice. Then from console started the verbose command. It still gave an Error 500.
1 Like
I’d be surprised if it’s rate-limiting, given that I signed up and sending the initial message immediately failed. Since sending messages to whisperfish also failed, I thought that maybe my registration didn’t work properly so I removed .config/harbour-whisperfish and .cache/harbour-whisperfish.
Now the app won’t start anymore:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: NoNumber', src/worker/client.rs:897:61
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[2021-05-17T15:22:02Z ERROR harbour_whisperfish::gui] Error handling StorageReady: Mailbox has closed
Bus error (core dumped)
Edit: Looks like it happens because I should have also reomved .local/share/harbour-whisperfish. I still think it shouldn’t just panic, though.
Make sure to remove both share and config at the same time if you want to 100% reset. While it shouldn’t panic, removing directories manually shouldn’t be needed either 
Receiving messages should just work though. If it doesn’t work, that sounds like a new issue, and you may want to provide some log excerpts to show what happens.
If I got it right, 0.6.0-beta1 should support groups v2, right? A contact (Android user) wanted to invite me to a group and got an error message. The message says something like “1 member does not support new group type, so the group can not be created” (I do only have the german message, so this is not the original one).
Is this expected or should the invitation work? Can I do anything to figure out what the problem is?
Yes, this was really my bad. Missed one directory while cleaning up. After properly removing everything I was able to start the app and go through the registration step again. In the end, this all results in the same familiar 500 errors.
The not being able to send from Android seems to be due to not having my landline as a contact in my phone. After adding the number as a contact it suddenly started working. So I can indeed receive messages, just not send them.
1 Like
It should just work, @inta. Did you only recently upgrade your phone? Because then it may take a while for the other clients to notice. I suggest you try again tomorrow.
I installed whisperfish for the first time on SFOS 4.1 and registered the account with 0.6.0-beta1. I’ll try it again the next days and report if it is working.
Wasn’t there a problem with invites and the group owner should just add the new user to the group instead of inviting?
Yes, but what @inta described sounded more like like the transitional thing. After a new registration, however, it should indeed work immediately, so there’s definitely something wrong.
Would there be a difference if the user ever had a Signal account before vs if if it’s the very first time they sign up?
Did you link an old version of Signal Desktop with your phone? If any linked device doesn’t support groups v2, you can’t be added to a group v2.
Ok, we tried again, both creating a new group and adding to an existing group does not work.
@rubdos can I somehow help you figure out what is going wrong with the groups?
@ichthyosaurus I’ve install the desktop client on two Linunx machines, both the newest version v5.1.0 but I could not find any information regarding group v2 support for those clients.
1 Like
The latest version/any recent version of Signal Desktop should work.
My best guess, currently, is that you were also affected by the HTTP 500’s, and that therefore you didn’t yet sync any profile key information.
Either that, or you’re somehow on an old version of Whisperfish (maybe double check in About). If you send some 1:1 messages to your buddy, then wait an hour or so, it should work. If it doesn’t, I suggest you get in touch with me on IRC/Matrix/email; it’ll get quite messy here otherwise
1 Like
Group invite is working now. Neither Whisperfish version nor desktop client version changed in between, so it seems to take just some more time.
If I were a betting man, I’d blame a potential Signal-Server bug.
@martijntje, @marcelpol, @orangecat, does sending work again for you?
I’m still getting the same 500 error, unfortunately.