[netsharc]

Can someone contribute more than "lol, me too!" and figure out which API endpoint it's hitting, what it's returning and guess why it's crashing? I don't have an iOS device otherwise I'd do it...

[acdha]

It’s their own “Safari suggestions” service. I don’t know if that’s device local or some Apple API which changed but disabling it prevents the crashes.

[bombcar]

I wonder if "Safari Suggestions" is crossing a privacy line with its API it shouldn't and iOS nukes the app from orbit.

[acdha]

I doubt that since it’s their own code but I’d easily believe that it hits an API endpoint which just started malfunctioning. The description is vague but it appears to retrieve a bunch of different kinds of information from some Apple service. Clearly a massive test coverage miss if my speculation is right.

[superjan]

I think he is joking.

[bombcar]

It's partially a joke, but as anyone who has worked with a complex system, things like this can happen. A privacy control is changed somewhere, but not activated until later, and suddenly one day something stops working.

[acdha]

I wasn’t sure about that and it’s certainly not without precedent that different parts of the same company might do something like that.

[dpkirchner]

Someone from Apple can probably attach a debugger and figure out the problem, but most of us are going to be in the dark.

[cozzyd]

set up a proxy, install its certificate and mitm it? Might work at least...