Safari version 13.0.4 enable cookies

Actually, it appears that Apple has fixed this bug in the next release it made on Monday 01/27/2020 (Safari 13.0.5 which is part of the macOS Catalina 10.15.3). For me at least, the websites that did not work in Safari 13.0.4 now do work in Safari 13.0.5 so no workaround is required anymore.

This is an official release version and not beta so it should be safe to use on your production partition but I thought that about 13.0.4 so I won't admonish you for putting it on a test partition first.

The issue is when a Bill Pay site opens in an iFrame. Safari 13.0.4 will not work with Prevent cross-site tracking unchecked. You can check the setting when on the blocked iFrame, close preferences, then reopen preferences and uncheck the setting and revisit the iFrame and it will work. I believe when you close Safari and try again it will be blocked again.

This definitely looks like a Safari bug to me.

Yeah I know but I have been scouring the internet since 13.0.4 came out and could not find any info about the bug or the plan to release 13.0.5. I even called Apple and they just suggested downgrading my OS version. Was this bug or 13.0.5 release information available anywhere?

This Forum Thread has been up since December 13, 2019 when I first encountered the problem not only with Bank Websites but with many other websites like lite on-line game sites. Apple rarely if ever directly responds to Bug Reports and simply quietly fixes them. This is not optimal from the perspective of many users, but it appears to be a pretty consistent Corporate Policy.

Personally, when Apple released Safari 13.0.5, I assumed they probably fixed this issue since it seemed to be a fairly widespread issue with most workarounds (other than using a different browser for affected websites) being both cumbersome and only working intermittently. For me, so far at least this has completely corrected the issue and the websites that worked correctly before 13.0.4 are now working again with 13.0.5

I would add that for me it was basically a few days over a month before they fixed it (12/13/2019 through 01/27/2020 which for me seems a pretty quick response.

I am using safari 13.0.5 and all is not well. I have to deselect website tracking and Apple Pay and Apple Card in safari preferences. Then I have to quit safari, log in again and select the two aforementioned boxes. Only then can I get into bill pay. And this whole thing must be repeated the next time I use bill pay. Does this give anyone a clue as to the cause of this problem?

That was my experience with Safari 13.0.4 but personally I have had Safari 13.0.5 since its release 01/27/2020 and it fixed this issue completely for me. Several other commenters on this thread have reported similar results. What you are describing sounds like the issues many were experiencing in Safari 13.0.4. I can not replicate the issue in 13.0.5. Perhaps someone else monitoring this thread has further insight. I certainly hope that my experience was not fleeting and Apple actually fixed the bug from 13.0.4 with 13.0.5.

Good Luck - if this persists the least cumbersome solution I found was to install a different Browser (either Google Chrome or Microsoft's newly released Edge for MacOS. I kept Safari as my default browser and only used Chrome or Edge for on-line banking/bill pay or for casual games that did not work in 13.0.4. Again, for me at least I have not experienced the problems any longer since Safari 13.0.5

Hope this helps and really hope yours is an isolated error.

Granville Alley

As a test, try Safari/Preferences/Privacy and uncheck Prevent cross-site tracking.

I have the same problem as skip259 and have the same computer with all of the same software and all of the same settings. I tried rebooting in safe mode and the problem remains.

I also tried the newly-created admin user approach and the problem remains. Sorry, just wanted to be clear that I've tried all suggestions that I can find.

You are welcome.

This worked for me! thanks!

Same problem. What's the solution?

I'm having the same problem with Mojave 13.0.4. So, not sure if upgrading is the answer.