Corrupt iCloud Data Causes iOS SpringBoard Home Screen Crash
This crash was happening regularly, sometimes as often as every 10 minutes. The Apple Store first recommended we wipe the device of all data and NOT restore from a backup. Problem still happened. Then the Apple Store replaced the device, and again we did not restore from a backup, and again, the crashes quickly resumed.
No restore from backup. Brand new hardware. Same crash. Diagnosing this just got interesting.
It turns out that Apple’s TextInput service uses Core Data and iCloud to store user dictionary entries such as shortcuts/abbreviations. His database became corrupt, which caused SpringBoard to crash. iOS doesn’t have any way to clean out this data, but he was about to do so from a Mac by digging into the Mobile Documents folder.
6 Comments RSS · Twitter
@charles Mine has a .cdt package with XML transaction logs.
"It turns out that Apple’s TextInput service uses Core Data and iCloud to store user dictionary entries such as shortcuts/abbreviations."
(my bolding)
So, if I'm parsing that correctly, this means Apple actually is eating their own (contaminated) dog food, at least a little bit. That's a first, no?
And predictably crashing iOS devices in the process...
Actually, I just realized you mentioned CoreData in your entry, but he does not. Are those cdt files CoreData transaction logs?
Sorry, I just checked Drew's article, and they are, so yes, interesting to see they were poisoned by their own dog food :-)
"so yes, interesting to see they were poisoned by their own dog food :-)"
One thing is for certain: there is no stopping it; the trend of Cupertino eating its own poisoned dog food will soon be here. And I, for one, welcome our new Fully Sandboxed Finder™ in 10.9 overlords. I’d like to remind them that as a trusted internet commenter, I can be helpful in rounding up others to toil in their underground sugar caves.
Too bad, my TextInput folder is empty. I am curious if there is a CoreData database on there :D