You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did you perform a cursory search of open issues? Is this bug already reported elsewhere?
Are you reporting to the correct repository (magic-sdk)?
๐ Description
Upon initializing the Wagmi connector into my project, I noticed a peculiar behavior related to cookie rendering.
๐งฉ Steps to Reproduce
Integrate the Wagmi connector into the project.
Initialize the Wagmi connector within the codebase.
Observe the rendering behavior of cookies.
Notice the continuous rendering of cookies without halt.
๐ค Expected behavior
I expected the cookies to render appropriately upon initialization and to cease rendering once initialized. There should be no continuous loop of cookie rendering.
๐ฎ Actual behavior
The cookies enter an infinite rendering loop, continually rendering without cessation. This behavior triggers an error marked with number of times it has rendered, indicating that the cookies have been rendered an excessive number of times. Consequently, this error warns that third-party cookie functionality may be blocked.
Yep, we're experiencing this issue as well, we recently upgraded https://github.com/magiclabs/wagmi-magic-connector in our project from 1.1.5 to 2.0.0, which it seems also comes with a magic SDK version upgrade.
Activity
Royal-lobster commentedon Mar 27, 2024
This seems to be a issue on almost all sites that has magic login integrations
hubagaspar91 commentedon Apr 17, 2024
Yep, we're experiencing this issue as well, we recently upgraded https://github.com/magiclabs/wagmi-magic-connector in our project from 1.1.5 to 2.0.0, which it seems also comes with a magic SDK version upgrade.
TheGreatAlgo commentedon May 24, 2024
Having same issue too. we were on 8.1.0 (time for upgrade lol) and having the issue
mjafri118 commentedon Jun 18, 2024
is there a fix to this? upgrading does not seem to help.
Wyxuch commentedon Jun 25, 2024
Hi there!
this bug still occurring in 28.0.7. Is there any chance to fix that in the upcoming updates?
bowis commentedon Oct 20, 2024
Same issue here still