This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Event being broadcasted but client wont pick up on it #187
Comments
After a lot of fiddling, the frame is now being received by the client. BUT .listen isn't picking up on it!
|
Hi! I think that your problem is that, by default, Echo Client listens to an event with namespace |
Nope. That's not it. I'm using the prefix "." syntax to escape the namespace. |
Plus the frame that's being received only says "messages.created" without any namespace |
This looks like a client configuration issue. Closing |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to broadcast a simple event using Redis, Laravel Echo, Laravel Echo Server, and socket.io.
I've got everything in place on the client side. The message is indeed being broadcasted and laravel echo server is picking up on it.
On chat.dev/ I have the client joining. On chat.dev/new I have the event being broadcast.
So it seems like everything is working. On the client side, I'm including socket.io and it is finding it.
<script src="//{{ Request::getHost() }}:6001/socket.io/socket.io.js"></script>
Then I'm running
But nothing is being logged to the console. Why?
The text was updated successfully, but these errors were encountered: