(This leads to the item never appearing in the UI on any other machine.) When this happens, bogus relationships get created between blob items and an arbitrary unrelated owner. Owner items get lost in synchronization and never appear on computers other than the one on which they were created. Owner relationships in an item’s data will point to the wrong owner In some cases (again, not all the time), iCloud may do one of the following: In some circumstances (and we haven’t been able to figure out which, yet), iCloud actually changes the object class of an item when synchronizing it. In general, when iCloud data doesn’t synchronize correctly (and this happens, in practice, often), neither the developer nor the user has any idea why. It involves so many departments and teams inside Apple that it makes for a very fragile system. I’m not here to say whether that’s right or wrong or fair or not or whatever, those are just the facts.Īnd, once you dig in, iCloud for developers is far less a completely holistic solution and much more of a loose bundle of networking protocols and systems that are unified in name only. One of them is used heavily inside Cupertino for its own services and the other is offered as a developer API and used only selectively for Apple’s own apps. So when I say that there are two iClouds, I mean that there are two iClouds. The assumption here is clear: you’re either using iCloud exclusively for data storage or you don’t want to use that data at all. And signing out of iCloud results in the system moving iCloud data outside of an application’s sandbox container, making it impossible for the app to use the data any longer. Doing this, it turns out, completely removes a user’s locally stored iCloud data. Opaque errors are just the beginning-developers are also frustrated with how iCloud handles a user’s data if the user chooses to turn off document and data syncing. They aimed high, but ultimately bit off more than they can chew. Rather, I don’t think they know how to fix the problem. The article insinuates that Apple doesn’t care enough to fix the problem. “Because of this there is a lot of fragility to the implementation, and I’m not sure it will ever scale well to larger data sets,” he said. So can these issues ever be solved? “ approach to the problem was very novel and interesting, and perhaps they will ship a version of it that works – but it functions very differently than typical sync solutions in that there is not a central server hub that maintains the ‘truth in the cloud,’” Pierce told me. WWDC 2013 is just around the corner, and while many of iCloud’s syncing issues have been fixed, dozens of bugs remain unsquashed. “Some issues with iCloud Core Data are theoretically unsolvable (stemming from the fact that you’ve put an object model on top of a distributed data store) and others are just plain bugs in the implementation,” he said. “Ultimately, when we looked at iCloud + Core Data for, it was a total no-go as nothing would have worked,” said one best-selling iPhone and Mac developer. Many veteran developers have learned their lesson and given up on iCloud’s Core Data syncing entirely. “AppleCare has been unable to assist our customers who run into these issues.” “Many of these issues take hours to resolve and some can permanently corrupt your account,” one top developer told me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |