-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
Argument 2 passed to Illuminate\View\Compilers\ComponentTagCompiler::__construct() must be of type array, object given #36816
Comments
Did you clear your views? |
Yes, I ran both |
Are you sure you're not forgetting to reload php-fpm or something? It seems to me that opcache or something might be a culprit here. We haven't had any reports from other people. This should be a fairly recognizable problem if it was really a bug. |
Yeah, I've reloaded/restarted it, and unfortunately, the issue persists. This was my worry -- it seems very obscure and specific to my case :( The issue occurred following the upgrading of Laravel, Horizon, Telescope, etc. so I might just downgrade back a couple of major versions and work up from there. I appreciate the help thus far. |
I have performed the necessary tests now and I did not encounter the problem you mentioned. There is probably a problem caused by a mistake you made. I tried it by installing one by one in order to test it and I did not encounter any problems. @romansorin I think review your actions again. |
@romansorin seems it's indeed specific to your use case so we can't help out here. Please try a support channel instead: |
Description:
After updating Laravel, Horizon, and Telescope to their new respective major version, I am no longer able to access the Telescope or Horizon dashboards (
/telescope, /horizon
). I published the vendor files/views after updating Telescope to 4.4.6 and Horizon to 5.7.3. When trying to access these endpoints, I receive the following error:I do not believe that this is an issue with Horizon/Telescope, but I'm lost in where to approach this, and cannot seem to find anyone else experiencing this issue through SO/Google.
Steps To Reproduce:
The text was updated successfully, but these errors were encountered: