When we use our smartphone in a poorly covered network area, like most of the Parisian subway lines, the following scenario happens quite often: we try to load a given resource (web page, json, etc.) and get nothing but an endless loading animation. However, after several tries, the resource just suddenly appears.
In our last blog post about Core Data features in iOS 8, we have learned about
NSBatchUpdateRequest. This time, we will dig into another new feature: asynchronous fetch requests.
If you ever use public transportation in Paris, you might have noticed the apparition of a slightly different Navigo pass since mid-January. This new pass stars a brand-new Philippe Starck design and first and foremost has a built-in NFC chip which is compatible with most Android phones (for the iPhone 6, the NFC API is currently exclusively reserved for Apple Pay).
Last June, Apple introduced iOS 8. And every new version of iOS comes with a bunch of new APIs. Browsing the full list of API differences between iOS 7 and iOS 8, we came across Core Data new features: batch update requests and asynchronous fetch requests. In this article we will focus on the first type of requests.