woocommerce-ios
woocommerce-ios copied to clipboard
woocommerce
EXC_BREAKPOINT: ☠️ [CoreDataManager] Recovery Failed! > configuration > Fatal error > Storage/CoreDataManager.swi...
Sentry Issue: WOOCOMMERCE-IOS-1CXX
EXC_BREAKPOINT: ☠️ [CoreDataManager] Recovery Failed! > configuration > Fatal error > Storage/CoreDataManager.swift > type
File "CoreDataManager.swift", line 109, in CoreDataManager.persistentContainer.getter
File "<compiler-generated>", in @callee_guaranteed
File "CoreDataManager.swift", line 94, in CoreDataManager.persistentContainer.getter
File "<compiler-generated>", in @callee_guaranteed
File "CoreDataManager.swift", line 74, in CoreDataManager.persistentContainer.getter
...
(75 additional frame(s) were not displayed)
![sentry-io[bot] avatar](https://avatars.githubusercontent.com/in/12637?v=4 "Published by a pub.dev verified publisher"){kind=small}
Just a note that the most recent reports of this crash are from 6.9.0.2. The 7.0.0.0 release has been available for 8 days with no crashes yet.
^ from few reports had suspicion it's not a crash. Was wrong, it always ends with fatalError().
Just a note that the most recent reports of this crash are from 6.9.0.2. The 7.0.0.0 release has been available for 8 days with no crashes yet.
N.B. this still happens in releases up to 7.9
As of Apr 7, 2022: 11,141 events with 879 events in the past 30 days (still happening in 8.8.0.1 release).
As of Apr 29, 2022: 12066 events with 603 in the past 30 days(still happening in 8.9.0.2 release).
Prioritization: Severity – high: crash Impact – low: 476/102k (14 days) 0.46% = medium
This is our biggest crash, so we could consider bumping it to high. I thought about it, and am erring on the side of leaving it as it is, since it's still only affecting a small portion of our users.
One argument for high is: if someone's going to work on a crash, maybe it should be this one... on the other hand, we would probably have more luck fixing issues we've not looked at before.
@astralbodies what do you think?
@joshheald Thanks for illuminating this crash! @shiki did a bunch of work to improve the Core Data stack and the crashes are definitely less. Sometimes this can be attributed to weird data model transformations or just unexpected things like restoring an app from an old backup and the model upgrade goes weird. In the end, I agree that the number of users is small. It would be nice to have a more stable "oh crap Core Data is really hosed, delete and recreate the storage without signing out a user" thing, if it's possible. But, I don't see it being a high priority yet unless this were more widespread.
