Safari Version 18.0 (20619.1.26.31.6) suck in the allow cookies loop

Safari Version 18.0 (20619.1.26.31.6) suck in the allow cookies loop

dankron
Shopify Partner
22 1 8

Hey guys, 

 

I just updated my MacOS to the lates version and now Safari Version 18.0 (20619.1.26.31.6) is stuck on the infinite loop of allow 3rd party cookies on the theme editor.

Screenshot 2024-09-19 at 10.06.41 am.pngScreenshot 2024-09-19 at 9.53.50 am.pngScreenshot 2024-09-19 at 9.53.39 am.png

 

Chatting to support, they are completely useless, keep telling me to turn off prevent corss browser and block all cookies, even when i have already shared screenshots showing those settings are off.

 

Replies 5 (5)

RealiX
Shopify Partner
1 0 0

Same for me, and I can't find any solutions...

RunGMhx
Visitor
2 0 0

Well, also in the same predicament, hopefully a solution or update emerge soon...

WillyMason
New Member
6 0 0

Yup same here. It's infuriating! Assuming this is more on Apple's side of the equation but Shopify gonna need to figure out a solution because a lot of store owners are going to be using Safari browser. Furthermore it is logging me in and out constantly too when I do code changes in the theme editor etc.

dankron
Shopify Partner
22 1 8

If you search a bit, this was an issue back in 2020 too, it got resolved I don't know how, but after this new update it looks like it's back.

With the constant logging out, that is another issue, but definitely on the Apple side of things, I have this issue too and it has something to do with the developer tools on safari, if you disable developer tools under settings it will stop logging you out, that's been happening for quite some time.

The other option to get past the logging out thing is using Safari Technologi Preview. It's annoying AF and hard to understand why Apple is not implementing this fix for the full version Safari... they definitely know a way to fix it (they did it for the technology preview browser).

But yes the cookie thing NEEDS to be fixed ASAP.

RunGMhx
Visitor
2 0 0

For the record, I tried again yesterday and it now seems to work fine even though it seems no actual update were made to safari.