'Same-site flags were removed in Chromium 91 - How can I disable them for local development?
Solution 1:[1]
there is an temporary solution for this problem set an commond line in chrome/edge (v91) launch cofing like this:
Windows?open Chrome/edge shortcut's property?add: "--disable-features=SameSiteByDefaultCookies" after Target property
in my pc,it like ** "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --disable-features=SameSiteByDefaultCookies ** finally
then restart your chrome/edge,try again
Solution 2:[2]
For the local development in chrome 91, we need to edit the cookie SameSite attribute and set it as None.

Solution 3:[3]
Starting from Chrome 91 these flags are not needed since it is now a default behavior. It means either this feature(s) must be configurable in settings or non-configurable at all (and this is our case!).
However, there are still similar launch feature flags available up until Chrome 94:
SameSiteByDefaultCookiesCookiesWithoutSameSiteMustBeSecure
For example, launch command in Linux then would be
google-chrome --disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure
I guess after Chrome 94 one has to just deal with it
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | ??? |
| Solution 2 | Sreekanth.S |
| Solution 3 | amankkg |



