I had a similar problem on my Electron application/browser side

• fetch's credentials: 'omit' solved the warning issue for me

// Example
await fetch('https://example.com', {credentials: 'omit'});

I am writing here because this is the first link in Google and I believe it will help people like me; xoxoxo

As discussed here: https://blog. chromium.org/2019/10/developers-get-ready-for-new.html

This is actually a server-side problem. What it means is that you are using a resource from another site (most commonly JS or CSS), and that server is trying to set a cookie; however, it does not set the SameSite attribute.

The reason for this is:

Since your post does not define whether you are working on the server side or client side, my assumption is that you are working on the client side and, therefore, there is nothing you can do since the resource needs to update it. However, if you are doing server-side development, here is a list of resources in different languages: https://github .com/GoogleChromeLabs/samesite-examples

TLDR;If you are a client developer, this is because the linked resource does not have this setting, and there is nothing you can do about it. If you are a server-side developer, check out the github link for examples on how to fix this for your site.

Edit: If you just want to remove the message, the solution is discussed here: Chrome Console SameSite Cookie Property Warning, you can deprecate the message via chrome://flags Cookie DisableDisable them.