Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`SameSite` attribute Warning
See original GitHub issueDo you want to request a feature or report a bug? I think is neither of those
What is the current behavior? I’m getting this warning, starting today, the date I’m creating this issue
A cookie associated with a cross-site resource at http://pusher.com/ was set without the
SameSiteattribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set withSameSite=NoneandSecure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar.
What is the expected behavior? There should not be a warning indicating that in the future the cookie won’t be delivered if the attributes are not set correctly
Which versions of Pusher, and which browsers / OS are affected by this issue? Did this work in previous versions of Pusher? If so, which?
"pusher-js": "^5.0.0"
Chrome Version 77.0.3865.90 (Official Build) (64-bit)
Thanks for reading this weird issue, and apologize in advance if it doesn’t meets the format, I would like to know if there is something I could do from the configuration perspective, to remove this warning, I’m using this configuration https://lighthouse-php.com/4.1/subscriptions/client-implementations.html#apollo
Issue Analytics
- State:
- Created 4 years ago
- Reactions:9
- Comments:21 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It seems there’s not an easy ‘fix’ for this issue at the moment. One workaround that you might try is disabling stats using the
disableStatsoption. This should prevent the library from sending the only request it makes to apusher.comdomain and should suppress the error. Could anybody confirm whether setting that parameter solves their issue?I had a look at this issue this morning. I was able to see the warning in a normal Chrome window but not in an Incognito window. Can anybody else confirm that they’re seeing the same behaviour?
This, along with the fact that pusher-js doesn’t really use cookies directly, leads me to suspect that this is an issue with one of the cookies set by the pusher dashboard, rather than a specific issue with pusher-js.
I’m going to take this to the appropriate team. I’ll post an update when I have one.