Updating managed object core data
Core Data already supports the situation where an external process alters a persistent store on disk; this is precisely how i Cloud works.When records are imported from i Cloud, the method.However, there is still no straightforward method of transmitting this information between app group members.Sample code referenced in this post can be downloaded here.Depending on how you use it, Core Data can either be your enemy or your friend: if done on the main thread, Core Data processing can significantly inhibit application performance.If you however decide to use it asynchronously, you better know some patterns.App Groups were introduced in i OS 8 to allow data to be shared between separate processes running on an i OS device.An app group can have multiple members — one or more standard i OS apps, extensions or Watch apps.
Content which is before you is the resulting work of my colleague Igor Stojanovic and me.This approach is effective but can make for a jarring user experience.If the user is viewing a table of data which is reloaded without warning this can be confusing, particularly if different data are suddenly shown with no animation to give a visual clue about what just happened.Here are some common solutions (stacks) found in practice.The first approach is a rather simple one: just have it all on main queue.
Search for updating managed object core data:
Note that although support for an XML data store exists for OSX, it’s not available on i OS. Be aware that all UI updates happen on the main queue, so any Core Data action (read or write) on the main queue will have an impact and might cause visual glitches or performance issues.