Same issue here, we followed exactly the same process as previous years and our certificate expires the 19th of February, has anything changed since then?

Hello, We have tried various ways to solve this issue to our customers; removing certs, reinstalling, over-riding the existing ones... and we have not being able to find a workaround to provide some steps to our customers to solve it. The issue is quite impactful and worrisome on our side, so I wonder, Have a workaround for the issue being identified (besides performing a factory reset)? How could we get to know an estimation from Apple to fix it? We are trying all the Beta updates hoping to have the issue fixed, but it looks like it won't be fixed in the upcoming release. So far it is unclear even if this issue is going to be fixed. For now I feel we can only cross fingers. Bests.

[quote='811930022, DTS Engineer, /thread/764673?answerId=811930022#811930022'] Based on your bugs we think we understand what’s happening here. As folks have noted on this thread, it seems to be related to updating from iOS 16 or earlier, either directly or from a restored backup. The system is not correctly handling the migration from an older form of its internal data structures. Most folks don’t see this because they’re updating from iOS 17, and the migration works correctly in that case. [/quote] I can confirm that one of my devices that had the issue was updated from iOS 17 to iOS 18. The device is still broken and I am trying every update available and still waiting for the OS update that fixes the issue. Heads up @DTS Engineer because the issue is not only related to iOS 16 or earlier, so it could happen that folks are not spotting the issue but something different. Hope this nuance can help to solve the issue. Thank you, Sergio.