Open handhikadj opened 4 years ago
did you start the laravel queue workers? https://laravel.com/docs/5.8/queues
definitely I did
by the way, this is my config/queue.php
<?php
return [
/*
|--------------------------------------------------------------------------
| Default Queue Driver
|--------------------------------------------------------------------------
|
| The Laravel queue API supports a variety of back-ends via an unified
| API, giving you convenient access to each back-end using the same
| syntax for each one. Here you may set the default queue driver.
|
| Supported: "null", "sync", "database", "beanstalkd",
| "sqs", "iron", "redis"
|
*/
'default' => env('QUEUE_DRIVER', 'sync'),
/*
|--------------------------------------------------------------------------
| Queue Connections
|--------------------------------------------------------------------------
|
| Here you may configure the connection information for each server that
| is used by your application. A default configuration has been added
| for each back-end shipped with Laravel. You are free to add more.
|
*/
'connections' => [
'sync' => [
'driver' => 'sync',
],
'database' => [
'driver' => 'database',
'table' => 'jobs',
'queue' => 'default',
'expire' => 60,
],
'beanstalkd' => [
'driver' => 'beanstalkd',
'host' => 'localhost',
'queue' => 'default',
'ttr' => 60,
],
'sqs' => [
'driver' => 'sqs',
'key' => 'your-public-key',
'secret' => 'your-secret-key',
'prefix' => 'https://sqs.us-east-1.amazonaws.com/your-account-id',
'queue' => 'your-queue-name',
'region' => 'us-east-1',
],
'redis' => [
'driver' => 'redis',
'connection' => 'default',
'queue' => 'default',
'expire' => 60,
],
],
/*
|--------------------------------------------------------------------------
| Failed Queue Jobs
|--------------------------------------------------------------------------
|
| These options configure the behavior of failed queue job logging so you
| can control which database and table are used to store the jobs that
| have failed. You may change them to any database / table you wish.
|
*/
'failed' => [
'database' => env('DB_CONNECTION', 'mysql'),
'table' => 'failed_jobs',
],
];
still nothing happened
@handhikadj Did you find the issue?
I am experiencing exactly the same: the laravel-echo-server debug log shows that the client joined the channel + the event was broadcasted, but on the frontend the event is not picked up by the listener.
Okay, so actually not exactly the same, as I can see the broadcasted event in the laravel-echo-server log.
You could try changing "ShouldBroadcast" to "ShouldBroadcastNow" to narrow down where the issue is happening.
@KristianI never think there's ShouldBroadcastNow
interface. okay thank you very much for that. gonna give it a shot
I resolved my own issue - it was due to the channel names being prefixed by laravel recently - see this thread: https://github.com/tlaverdure/laravel-echo-server/issues/400 - it could potentially be of your interest , too.
anyway this is my:
.env
my event
laravel-echo-server.json
my shell
bootstrap.js
app.js
my step to produce is I created a dummy route to test the event via postman but still cannot log any messages to the console. please help!
note: I'm on mac mojave