Filed under: Bad Apple, App Store, SDK
Sometimes Auntie TUAW gets emails from anxious iPhone developers. In this case, the correspondent is running into issues with Apple's new automated checks for private API use in iPhone apps.Dear Auntie TUAW,
I got an email from Apple's App Review team saying the code in my iPhone app uses private APIs. They pointed to
-setOrder, which is a method I created in code, and -setThumbnail, which was created automatically from a Core Data property. But those are all from my own code, and thumbnail is actually a property for my CoreData class. Any idea why? I don't even have a setter for thumbnail, it is just a dynamic property for the CoreData class.
I don't want to rename my properties because I'm not sure that CoreData will automigrate my renamed items and my users are going to start crying if everything breaks.
Love & snuggles,
Lauren
Read on for Auntie's reply.
Continue reading Dear Aunt TUAW: My "private" APIs... aren't
TUAWDear Aunt TUAW: My "private" APIs... aren't originally appeared on The Unofficial Apple Weblog (TUAW) on Thu, 26 Nov 2009 13:00:00 EST. Please see our terms for use of feeds.