Replies: 3 comments 3 replies
-
How is this serialization been done? Queue? |
Beta Was this translation helpful? Give feedback.
1 reply
-
4 days later the issue is gone. Not certain as to why just yet. |
Beta Was this translation helpful? Give feedback.
2 replies
-
composer require laravel/serializable-closure |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello all,
This morning my application started encountering this issue when attempting to upload files:
Your serialized closure might have been modified or it's unsafe to be unserialized. {"exception":"[object] (Laravel\\SerializableClosure\\Exceptions\\InvalidSignatureException(code: 0): Your serialized closure might have been modified or it's unsafe to be unserialized. at /../../../vendor/laravel/serializable-closure/src/Serializers/Signed.php:83)
In the past when this issue appeared, I would regenerate the keys and then clear the route, cache, config, and view, then the problem would be fixed.
Any idea how to fix this? I've gone through all the recent changes, and I don't see anything that could've caused this.
Edit note: This problem only occurs on my dev server; my local development environment is not encountering this issue.
Beta Was this translation helpful? Give feedback.
All reactions