cookie is not set in the browser

[Sumukha210]

Even though the cookie is present with response, the cookie is not setting the browser. I am also setting credentials to true.

const client = createClient({
  url: "http://localhost:4000/graphql",
  fetchOptions: {
    credentials: "include",
  },
});

app.use(
    cors({
      origin: "http://localhost:3000",
      credentials: true,
    })
  );

I am also setting the cors in the server

[okxle]

I am also currently facing this issue. Are you able to solve it?

[jacklynch00]

Wait same! Is anyone able to solve this, driving me crazy!

[tastycrayon]

const httpLink = createHttpLink({
  uri: "http://localhost:4000/graphql",
});
const authLink = setContext((_, { headers }) => {
  const token = getAccessToken();
  return {
    headers: {
      ...headers,
      authorization: token ? `Bearer ${token}` : "",
    },
  };
});
const client = new ApolloClient({
  link: authLink.concat(httpLink),
  credentials: "include",
  cache: new InMemoryCache(),
});```

[pranta-barua007]

@benawad
I hope you're having a great time. The browser is rejecting to save the cookie
hey there are some major changes in CHROME while saving a cookie, it has changed it's requirements.
Please FIX this issue!!! 😥

UPDATE by CHROME : https://www.youtube.com/watch?v=GPz7onXjP_4
REF: https://medium.com/swlh/7-keys-to-the-mystery-of-a-missing-cookie-fdf22b012f09

[ashtonland]

I had this issue a couple months ago to and it took ages to fix😭, its been a while new so i can't remember exactly what the problem was... but these are things I changed in an old commit to fix the cookie not being sent,

1st, I had to set the app's trust proxy to the opposite of the production env, in hindsight I'm not sure if you really need this

const initServer = async () => {
    const app = express();
    app.set("trust proxy", process.env.NODE_ENV !== "production"); //👀❗

    const corsOps = {
	origin: "http://localhost:3000",
	credentials: true,
    };

*I had switched to the built it cors, thinking that was it ,but since then I have switched back so that wasn't the issue

Then I eventually found out that I needed, as @pranta-barua007 revealed above w/ the chrome update, the samesite and secure properties on the cookie, because cors would block cookies sent from another domain (localhost:4000).

res.cookie("pid", token, {
    path: "/refresh_token",
    httpOnly: true,
    sameSite: "none", //the
    secure: true, //special sauce
});

And later on, when fetching the refresh token from the server, I added mode: "cors", or it was blocked by cors

...
fetch(process.env.NODE_ENV === "production" ? "<prod url, probably hosted w/ heroku>/refresh_token" : "http://localhost:4000/refresh_token", {
    method: "POST",
    credentials: "include",
    mode: "cors", //this guy right here
}).then(async (x) => {
    const { accessToken } = await x.json();
...

I remember this was a true pain so hopefully this is able to help you guys 😇🤞