Thank you, we'll look into using MKLocalPointsOfInterestRequest. Do you have any idea about why this happening only on the CI machine?

Do we have docs for this already? It seems the keychain keeps the items but I couldn't find any documentation around the time it stores before deletion.

Still happening here. In my case, I have CoreData hooked up to a UITableView, so the crash was the infamous Invalid update: invalid number of sections. The number of sections contained in the table view after the update (2) must be equal to the number of sections contained in the table view before the update (2), plus or minus the number of sections inserted or deleted (1 inserted, 0 deleted). For some reason, the CoreData transaction would be finished at the wrong time, causing the crash. You can imagine how many hours I spent on it...

Also worth mentioning that in my case I tested with a string without any HTML, even with an empty string the issue would happen sometimes.

Should we keep it always enabled for CoreSpotlight integration too? I want to gate this using a feature flag.