-
Notifications
You must be signed in to change notification settings - Fork 44
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
'New session ID expected.' error #38
Comments
That sounds odd. If you dump the
You have to have the Chrome can also be remotely debugged over a USB cable to access the network request log allowing you to see what the communication is between the client and the server, what cookies are being sent/received, what errors, if any, show up in the Console log. |
This issue is only getting worse, although it's only seems to affect Chrome on mobile at the moment. As requested, here's $_Cookie before throwing 'New session ID expected. Most likely cause: Cookies are disabled or bad provider.' array ( |
Some more logs from the last hour: |
Those are three different issues. The first three are not setting/accepting the Out of curiosity, do you have other cookies in |
After ensuring our code is unmodified (except for logging) and leaving it for a week - here are some logs from this morning. There are many more entries, so this is becoming a fairly major problem. I've shortened identifier strings, but you can see where they are the same. [14-Nov-2022 10:05:11 Australia/Perth] New session ID expected. Most likely cause: Cookies are disabled or bad provider. array ( In answer to your questions: Thanks :) |
Another thought: How about PHP error/warning logs? If PHP is emitting headers BEFORE setting the cookie for whatever reason, then the cookie won't be set/sent. Did you mean to close this issue? |
Sorry, closed accidentally. There are no other PHP errors being logged to file. I'm yet to see this issue on desktop browsers; I'm concerned this may be a staggered release of a new behaviour in Chrome/WebKit. |
We've started seeing the 'New session ID expected. Most likely cause: Cookies are disabled or bad provider.' error when logging in via mobile devices.
Is this due to Chrome disabling third-party cookies (https://www.cookiebot.com/en/google-third-party-cookies/) and SetCookieFixDomain being called without a value for the domain parameter (and hence the cookie not having a domain specified)?
Would it be relevant to incorporate SameSite=Lax on the cookie?
The text was updated successfully, but these errors were encountered: