Credit Card AutoFill Crashes WebKit Process on Safari 26.0.1

Question

Level 1

39 points

Credit Card AutoFill Crashes WebKit Process on Safari 26.0.1

After updating to Safari 26.0.1 on macOS Sonoma 14.8.1, any attempt to autofill a form with a saved credit card will cause the WebKit process to crash. This happens as soon as AutoFill has been authorized via Touch ID or manual password entry. The web page then instantly reloads with the dreaded “This webpage was reloaded because a problem occurred.” banner along the top.

This logging in Console.app seems relevant:

Warning: Exception caught during handling of received message, marking message invalid .
Exception: +[WBSFormDataController getCreditCardControlValuesForFillingInWebView:originatingInFrame:forForm:withMetadataProvider:andCreditCardData:completionHandler:]: unrecognized selector sent to class 0x1f3ba0b70
Received an invalid message 'RemoteObjectRegistry_CallReplyBlock' from the WebContent process with PID 55975
AuxiliaryProcessProxy::terminate: PID=55975
0x1114dc240 - ProcessAssertion::acquireSync Trying to take RBS assertion 'XPCConnectionTerminationWatchdog' for process with PID=55975
0x111c98b80 - [PID=55975] WebProcessProxy::didClose: (web process 55975 crash)

MacBook Pro 14″, macOS 14.8

Posted on Sep 30, 2025 1:41 PM

Reply

Answer 1

BSD Guru

Level 1

14 points

Nov 7, 2025 10:57 AM in response to Kolodner

Ok, I upgraded just safari that didn’t fix it.

Reply

Answer 2

BSD Guru

Level 1

14 points

Nov 9, 2025 9:30 PM in response to Jason Heiser

Adding insult to injury, 26.1 is also still randomly crashing, so the update didn’t fix a (darn) thing that I needed fixed.

Reply

Answer 3

Dec 19, 2025 8:52 AM in response to Kolodner

Tahoe is not supported for non M Chip computers. Mine is prior to the M Chip. Safari was working fine on all of our computers before Apple's upgrade. They need to fix it for everyone, not just those on the latest OS with the latest hardware.

Reply

Answer 4

Dec 19, 2025 9:20 AM in response to heelz

Thanks, but that’s a drastic measure. Many of us aren’t willing to take, especially if Apple requires us to do it after upgrades. Who’s to say that this won’t happen again, perhaps with Apple Mail next week. I say again, come on Apple, fix this stuff.

Reply

Answer 5

BSD Guru

Level 1

14 points

Dec 19, 2025 9:46 AM in response to Kolodner

Of course, because 26.1 was designed to run on Tahoe. They shouldn’t have released it for previous OS versions. It’s Apple being a greedy corporation. They want to force everyone to upgrade their macs.

Reply

Answer 6

BSD Guru

Level 1

14 points

Dec 19, 2025 9:54 AM in response to timauthee1

This is wrong. My 2020 mac is supported. As with every new release, some older macs won’t work. Its Apple’s systematic way of making people abandon perfectly good system

Safari has to go. Time to move on to Chrome so we get have a working browser with Sonoma or Sequoia or Tahoe with our Intel macs. Safari is really the only thing that become antiquated. I have a 10 core Intel i9 and there’s really no reason for me to dump this so I can use Safari. Some web sites don’t support Safari as it is.

Reply