-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is Tinder/Scarlet alive? #119
Comments
0.2.x is still experimental. to grab a non-snapshot version, 0.2.4 is still available via jitpack. Hopefully I'll have time to publish 0.2.5 soon. Scarlet powers Tinder's messages/matches every single minute. If you have issues integrating with it, can you create separate issues or link to existing issues, so we can triage those tickets and prioritize bug fixing. |
@aaronhe42 thanks for the response. 2nd is similar to it, the difference only that when our backend closes WS connection with special code (so client knows the reason), I can't initiate reconnection from the client with the call |
@aaronhe42 any progress? who could merge into 0.2.x , for example, |
any news? no commits |
Waiting for updates in 0.2.x branch |
is there any updates about #80 ? |
Guys I think we should create a new web socket library based on this one. It's ridiculous how they don't care about this project. I have seen so many good PRs and issues with no answers. |
Seriously what is going on |
Is Tinder/Scarlet alive?
Who is responsible for approving PRs? I've spent a lot of time for adding this library in my project, but now I'm stuck with some critical issues:
I much appreciate greate work that was done here, gson adapter, coroutines, retrofit-like config, but now I'm very doubt of using it in production.
The text was updated successfully, but these errors were encountered: