Problem repeatedly occurred" error in Safari 14.1

Since my last post was deleted as a rant or complaint that was not constructive, I've made another attempt below.

This issue has prevented me from using safari to: register a child for school, pay bills and even research this problem. Please advise of a fix that is not reinstalling the OS. That is a time consuming step that should not be needed to address something Apple broke with an update.

I agree with you 100% - this is insane. My computer was working perfectly until I did this update. The answer from Apple is to Reinstall the operating system. I am on Catalina and I found out from a friend that even if you upgrade to Big Sur the problem is not corrected. I tried all suggestions.

This is the most ludicrous suggestion that I can imagine as a developer. The amount of work that I'd have to undertake to "reinstall" is unbelievable.

Moving to FF or Chrome, although a great suggestion from a stability standpoint, sucks from a functionality standpoint if you're using keychain as your password manager as those browsers are not integrated. So great that I can use them to access ebay, or any of the other myriad sites that are blowing up Safari, but to do so, I have to manually access keychain in order to copy pasta my credentials.

Apple just needs to first update their integration tests so that the behavior is triggered, and then fix Safari. That way we don't see this problem again.

@ettocs I agree 100% with you, it is a HUGE amount of time and effort. Reminds me of the #1 solution when dealing with MS Windows! In my search for a solutionI found reinstallation is the #1solution in many posts and I refuse to waste the time. The number of people who have posted that they had Apple Support tell them to reinstall is baffling. I have several production apps that involve kernal extensions and I fear a reinstall could lead to the need to reinstall several other apps.

I prefer Safari for many reasons and this failed update is a real disappointment. I am going to test changing libwebrtc.dylib to a more recent version but disabling System Integrity Protection is not for the faint of heart!

Prost

This seems to only happen with Catalina and Mojave. It's a real pain, and makes Safari basically unusable. I wonder how this slipped past quality control. Disabling Javascript fixes the issue, but at the expense of most sites no longer working properly. I hope an official fix arrives soon.

That isn't happening on your computer. That's happening on your mail provider's server.

IMAP is Internet Message Access Protocol, it's a standard for managing and retrieving messages from mail servers.

Basically it is saying it couldn't copy (i.e. move) a message from your Inbox to the Deleted Messages folder, because the connection timed out (it took over 30 seconds).

Just to chime in here... Can't log into my bank any longer and many other sites don't work.

The browser keeps redirecting somewhere and then just stops.

Latest Mojave.

Apple seriously needs to fix this pronto. I don't want to upgrade my entire OS just because Apple broke their browser.

If the browser is not usable in its current form on Mojave - then don't ask me to update it on Mojave!

Same problem for me. Catalina 10.15.7. Safari 14.1. ebay, att.com, mlb.com, cnn, probably many others. Ironically, the MacRumours site is affected as well. Using Chrome until they fix this. Ugh. I was forced to do the update when I got my new iPhone 12 Pro this week.

djogon, My reply was in no way rubbing in the fact that you still have an problem without a solution. Just that Apple is aware of the issue as they have pulled the faulty Safari update, and that it will be rectified soon. I do however have a potential solution for future use. As I have discovered, through much dismay in the last 5 years, Apple is not reliable in their public releases as much as they used to be. I would suggest that people shut off automatic updates and wait a minimum of two days before they update anything. This has aided me in the past, and just helped me again with this lame Safari release... soon to be re-released.

I have the same problem. I did the update on Mojave from Safari 13.xx to 14.1 and now it crashes almost in all website... if I deleted all the cookies then it works fine but as soon as the cookies begin to install, the crashing begin again... it feels like the only option is to downgrade to Safari 13.x

Telling people to reinstall the OS is rather ridiculous. Apple needs to fix what their update has caused. I'm having the same issue on my Mac Book Pro running Mojave, but for what ever reason my iMac also running on Mojave is fine. And same as everyone else everything was fine until I did the update.

Same problem for me. Took the Catalina 10.15.7 update and got Safari 14.1. Now it's worthless on my MacBook Pro 16". Time to change Default Browser to Firefox or Chrome until Apple gets around to fixing it (don't hold your breath... seems to be a recurring issue for them)

Since this section of the forum is labeled Mac OS and the poster referred to running Catalina and his MacBook Pro I would expect that the presumption is that the problem we are referring to is on Macs.

Out of sheer obstinacy I spent an hour or so yesterday seeing if I could find out from Apple support whether anyone could estimate the time it will take to release a patch, to help decide what workarounds to adopt. After slowly elevating up through several levels I did reach someone who acknowledged this was now a known problem, and that there are valid reasons (i.e. mission-critical 32-bit legacy applications) that some users do not wish to upgrade to Big Sur, which was the solution offered repeatedly along the way. But no answer as to if and when to expect a fix.

Your post seems to indicate that the Apple attitude was that everyone should update to Big Sur and anyone who doesn't is expendable as a user / customer. I've long thought that Apple is building consumer media player devices and that any other use ( such as in my case pro audio and music applications ) and application vendors are simply hanging on for dear life around the edges. Funny if a bit grim to see that confirmed in actual language from Apple reps. I make a point after more than thirty years of using Macs to stay at least one if not two revisions of OS behind the current because my livelihood very literally depends on it.