-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Crash on XLLocalDataLoader objectAtIndexPath #21
Comments
Hey @mtnbarreto, we might be seeing this in iOS Orchid, can you take a look and respond please? CC: @ppaulojr. |
Hey @yuningalexliu, @ppaulojr , It seems to me based on the error Sometimes when we use a private context on a background thread that takes some time to perform a sync ( insert, update, delete) and at the same time we flush the database we get this error. Could you please check that these kif tests are not deleting the persistent store? We have been using XLData for the last 5 month now. I strongly recommend us to migrate XLDataLoader code to XLData. XLData is fully tested and solid enough for production apps. The only problem is it requires iOS8 and up due to it uses UISearchController class which is only available on iOS 8 and up. |
Thanks @mtnbarreto for responding! I think we can consider migrating to XLData once iOS9 comes out, right now we still want to support iOS7 until then due to our market :/... (we still have about 10% of our customers on iOS7) |
I was writing the same @yuningalexliu wrote. Unfortunately we still cannot use XLData |
@mtnbarreto I understand that this Library is being deprecated in favor of XLData. We plan to use XLData not in the upcoming version because we do need to support iOS7 but two versions from now. In the meantime what I'd like to ask is:
cc: @yuningalexliu @HelOlhausen |
Hey @ppaulojr
I'm not encouraging anyone to use it instead of XLData for new projects (that's why I labeled it as Deprecated).
XLData provides more functionalities than XLDataLoader, such as memory data sets so you should put your focus on Local and Remote Core Data Data sets. Basically we threw away XLLocalDataLoader and made some usability and stability improvements. The basic idea is still the same. The new concept that XLData introduces is the memory data sets, that are very helpful for creating either a "static" tableView/collection view (like a sliding menu) or a dynamic remote populated table view that keeps the data in memory and does not use core data. I would love to help as needed, If you want to know more about how to migrate to XLData we can schedule a meeting and go through the necessary steps. Honestly, my first guess is that this issue is not directly related with XLDataLoader. Core Data issues are hard to solve and sometimes to reproduce. As I mentioned before, I'm happy to help if you can isolate the issue. |
Just for documentation our crashes on XLDataLoader began when we changed from: e6e450b to: dd36983 We'll revert to e6e450b and if our crashes disappear we'll have strong evidence that the problem is contained in this diff: e6e450b...dd36983 |
Function failing: 8 Orchid 0x0037c9d7 -[XLLocalDataLoader objectAtIndexPath:] + 215
I would guess it's a synchronization bug.
Version used:
e6e450b47275ac067a6e8d7b4dd7fa1874be2ff4
The text was updated successfully, but these errors were encountered: