-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Return value of Spatie\Valuestore\Valuestore::all() must be of the type array, null returned #23
Comments
Dear contributor, because this issue seems to be inactive for quite some time now, I've automatically closed it. If you feel this issue deserves some attention from my human colleagues feel free to reopen it. |
It might be a little late and I hope you have already solved the problem, and for others having the same issue, |
Could you be more specific about how to solve this? |
I'm running into this issue as well, and it's really difficult to debug as it seemingly randomly throws this error. @jason-guru I think your solution is for when you I initially thought that this error was caused by 2 processes that simultaneously tried to update the @nuz did you eventually solve it? |
Finally I removed the package and put my values from database to config file. |
Return value of Spatie\Valuestore\Valuestore::all() must be of the type array, null returned Can you please help me to fix the above error. |
I fixed it by encoding the data in my array to utf-8. (cfr example function from Stack Overflow)
|
* make sure to all() method are always return an array * Update ValuestoreTest.php Co-authored-by: Freek Van der Herten <freek@spatie.be>
Hi, we just started using this on a site and during development we have had no problems with it, but we set it up on production, and set an error tracker, and it seems like every now and then we get a weird error from this.
It feels on a put line in the settings provider:
The line it always fails on is:
$this->app->settings->put('registration_year', $year);
and the error is alwaysSo far we haven't managed to recreate it, but it bothers me....
any chance you know what could be causing it? thanks!
The text was updated successfully, but these errors were encountered: