[bug]: getting warnings in Console

[adityabhattad2021]

Link to minimal reproducible example

https://github.com/StabilityNexus/FairFund/tree/main/app/web-app

UPDATE 27-08-24 :(No need for reproducible example)

Slack: https://walletconnect.slack.com/archives/C03RVH94K5K/p1711033563634099
Github issues:

• [bug]: getting warnings in Console  #2457
• https://github.com/orgs/WalletConnect/discussions/4546

Summary

I am getting multiple warnings in console regarding cookies, multiple versions of lit loaded, etc:

• Cookie “tld” will soon be rejected because it is foreign and does not have the “Partitioned“ attribute. 4211-ce6469b138bf3458.js:1:24931
  Partitioned cookie or storage access was provided to “https://auth.magic.link/send-legacy?params=eyJBUElfS0VZIjoicGtfbGl2ZV9CMDgwRTlEQzMxRTU4NzVFIiwiRE9NQUlOX09SSUdJTiI6Imh0dHBzOi8vc2VjdXJlLndhbGxldGNvbm5lY3QuY29tIiwiRVRIX05FVFdPUksiOnsicnBjVXJsIjoiaHR0cHM6Ly9ycGMud2FsbGV0Y29ubmVjdC5vcmcvdjEvP2NoYWluSWQ9ZWlwMTU1OjEmcHJvamVjdElkPTQ3MTI3OWM5NzYxM2FkYmY3ZWRkYjBjNGZlZWEzOTU2IiwiY2hhaW5JZCI6MX0sImhvc3QiOiJhdXRoLm1hZ2ljLmxpbmsiLCJzZGsiOiJtYWdpYy1zZGsiLCJ2ZXJzaW9uIjoiMjguMC4zIiwibG9jYWxlIjoiZW5fVVMiLCJtZXRhIjp7InByb2plY3RJZCI6IjQ3MTI3OWM5NzYxM2FkYmY3ZWRkYjBjNGZlZWEzOTU2In19” because it is loaded in the third-party context and dynamic state partitioning is enabled.
• Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self' 'nonce-2SdkO9PRFB5JkfMp8pBhHmc8iWhZxzJiZ0qSsvZqskk=' 'unsafe-eval' 'report-sample' https://*.magic.link/ https://cdn.segment.com/ https://cdn.amplitude.com/ https://www.google-analytics.com/analytics.js https://accounts.google.com/gsi/client https://*.launchdarkly.com/ https://www.google.com/ https://*.paypal.com/ https://www.paypalobjects.com/ 'sha256-O2Z/Int2dnWQI+JpBc4hIRlC7oBedig41hu/v71CM38='” inpage.js:1:334480
• Cookie “dd_cookie_test_a287c608-6069-4808-8596-46857ddfc90f” will soon be rejected because it is foreign and does not have the “Partitioned“ attribute.
• GET https://rpc.walletconnect.org/v1/profile/reverse/0xc3b8E2E891a006949b8Bd6F8F472d63b1C953A8B?projectId=471279c97613adbf7eddb0c4feea3956 404 (Not Found)
• layout.js:5742 Multiple versions of Lit loaded. Loading multiple versions is not recommended. See https://lit.dev/msg/multiple-versions for more information.

UPDATE 27-08-24 :

• https://walletconnect.slack.com/archives/C07838NJA22/p1724083523453769

  

• Discord about profile/reverse issue :

  • https://discord.com/channels/492410046307631105/1105316298390511626/1266781941496021064
  • https://discord.com/channels/492410046307631105/1258958507487658005/1258958507487658005

• Github issues:

  • [bug] GET return 404 from https://rpc.walletconnect.com/v1/profile/reverse/xxx #2347
  • [bug]: getting warnings in Console  #2457

• Magic Slack

  • https://walletconnect.slack.com/archives/C051V991N5A/p1722093056178989?thread_ts=1716313795.017479&cid=C051V991N5A
  • https://walletconnect.slack.com/archives/C051V991N5A/p1722093564594189
  • APKT-243

UPDATE 4-09-24 :

• [GUIDE NEEDED] How to get wallet provider from Appkit v5.1.5 #2793
• Getting 1000s of warning on console #2794

I was using 5.0.11 and it was throwing Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox. (10000+ times)

List of related npm package versions

"@web3modal/wagmi": "^5.0.3",
"viem": "^2.16.0",
"wagmi": "^2.10.4",
"@tanstack/react-query": "^5.18.1",

[linear]

APKT-656 [bug]: getting warnings in consile

[rust-master]

I also have been facing this issue and unable to resolve it yet.

GET https://rpc.walletconnect.org/v1/profile/reverse/0x69d20d81577A0dc94f622d439147233FfFD8c4Ff?projectId=d9ab4f9c4fd16c4c376ff4c5c4fce213 404 (Not Found)

[kuchaow]

Same here, multiple warnings in console.

[naxida-eth]

I am also seeing a continuously looping warning in the console.

[ultratestbro]

same for me 🫠

[rtomas]

Thanks for reporting. We know about this issue and we are working on it.

[RobertDaleSmith]

Thanks for reporting. We know about this issue and we are working on it.

Any kind of temp workaround we can apply to prevent the flood of warnings? Or just need to hold out for an updated release?

Thanks 🙏

[brianonchain]

Temp workaround is go to Chrome settings > privacy and security > third party cookies > add "localhost:3000" to sites allowed to use third party cookies

[ardasevinc]

please keep this open as its still an issue