-
Notifications
You must be signed in to change notification settings - Fork 66
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
Not getting ActionCable connected() when using litecable adapter #59
Comments
I think I had a similar issue but this should be fixed on master by #41 |
Yup switch to the master branch fixes this. Maybe we could have a new version released that has a functioning LiteCable implementation. |
Also would be really helpful to add a changelog entry stating this fix. |
@adrienpoly I see that you were trying to add a spec for this regression in another project adrienpoly/rubyvideo#50 Would be awesome if maybe we could get a spec for this inside the litestack repo itself. |
For sure yes I wanted to build a dummy app to add to the project but clearly running out of time right now. I f you can propose something that would be great for sure |
Yeah sure, I have the dummy app setup in all my other gems, so I can whip up a PR to get something going. |
Added some PRs to resolve a few of these items |
I am planning a new release soon that will include all the pending fixes/improvements, just checking what else I can sneak in |
In development when I switch to
adapter: litecable
inconfig/cable.yml
then it is not calling theconnected()
function. It does successfully call theinitialized()
function.Everything works correctly when I switch back to
adapter: async
where I getconnected()
andreceived()
I am using
puma
gem for development server on Rails 7.1. Let me know if there is any other information that would be helpful.The text was updated successfully, but these errors were encountered: