You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since upgrading to v4 I noticed that jobs that implement the ShouldBeEncrypted contract now fail, throwing an error when being processed:
unserialize() error at offset 0 of XX bytes
Digging deeper, I can trace this back to Spatie's IsTenantAware function. It appears the payload is still encrypted when IsTenantAware tries to unserialize it, so the unserialize fails (throwing the error above).
Again, wasn't an issue with v3, is an issue with v4, and haven't had a chance to dig deeper into what has changed in your codebase between the versions.
The text was updated successfully, but these errors were encountered:
I had no issues with v3.
Since upgrading to v4 I noticed that jobs that implement the ShouldBeEncrypted contract now fail, throwing an error when being processed:
unserialize() error at offset 0 of XX bytes
Digging deeper, I can trace this back to Spatie's IsTenantAware function. It appears the payload is still encrypted when IsTenantAware tries to unserialize it, so the unserialize fails (throwing the error above).
Again, wasn't an issue with v3, is an issue with v4, and haven't had a chance to dig deeper into what has changed in your codebase between the versions.
The text was updated successfully, but these errors were encountered: