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
Undefined property: stdClass::$channels v5.0 #295
Comments
Can you tell me which version of Laravel you're using? there's an incompatibility between version 5 and Laravel, fixed in Laravel 8.29.0. |
I'm a little confused regarding the Pusher.php snippet. Line 538 on |
@elverkilde Thanks for the quick reply! I'm using the Lumen framework from Laravel which is a lightweight Microservice framework, but it follows the original Laravel docs for the most. That one is running on version 8.2.3 ( The Pusher.php snippet I'm on about is located in It does look an awful lot like the one you just sent, but mine looks like this:
I've checked the My composer.json looks like this:
I've tried to run a So I don't know where this goes wrong. I guess for now I might create a custom pusher.php in my Docker structure so it overwrites the original. Sorry if I'm being unclear. If you need any more info let me know. |
sorry, I just did a test with a clean composer.json with I will keep this issue open until I have removed the buggy version from packagist. |
Deleting releases is a bad practice. Anyone who puts |
I was thinking the same, thanks @GrahamCampbell. I was looking for a way to mark it as broken in packagist, but it doesn't seem to be possible. I suppose leaving it is my only option? I did test a fresh composer.json with |
Yes, because |
Understood, thanks again! |
Yeh, there is no way to mark a package version as broken. People should assume new patch releases contain bug fixes, so should always use the latest version of a package, and not hardcode an old version in their composer.json. The purpose of the composer.lock file is to lock dependency versions at a known state for apps, so there's no reason to hardcode versions. :) |
@jordyvanvijfeijken I am going to close this issue, assuming things will start working once you change the version to |
@elverkilde @GrahamCampbell The issue lied with the composer file indeed. I changed this in my
To this:
And now it works and I get the newest version (5.0.3) after running a Thanks for helping me out! Just leaving this here in case anyone else encounters the same issue as me. |
Hello,
First of all, I'm using Pusher version 5.0
"pusher/pusher-php-server": "5.0"
with Lumen versionLaravel Framework Lumen (8.2.3) (Laravel Components ^8.0)
. My PHP version is 7.4.16.I'm making a POC with Lumen and Vue.JS. For now it just has to send a "hello world" message from the Lumen back-end to the Vue.JS front-end (which works). I have made an event which is triggered upon loading the page like this:
The MessageEvent looks like this (got this from the Pusher getting started help):
This part is working, since I'm receiving this in the Vue.JS application:
Now comes the problem when I check the queue log. triggered with
php artisan queue:listen
, I see the following:When I check the Lumen log files it says the following:
So I went ahead and checkt the Pusher.php file:
I decided to check what $response was, it gives the following:
Of course it can't get to $result->channels if response["body"]["channels"] doesn't exist.
When I go and check the Pusher API reference it says the following:
Which would mean that the body should indeed contain a JSON response. But when I scroll a bit further I see this:
Which should mean you don't have to set the info parameter, since it's optional and experimental.
The response it expects with the info parameter set is this:
Which is the channels object asked for. Which is not returned cause I don't set the optional
info
parameter.The text was updated successfully, but these errors were encountered: