Well, the objects they really don't want you using (that grant access to resources with no public API) are often exposed as shared instances via class methods.

Well, the objects they really don't want you using (that grant access to resources with no public API) are often exposed as shared instances via class methods. This is actually the case with PhotoLibraryServices, the framework with these private methods[1]. In general, I agree with what you're saying. My point here is really just this approach to detecting private API usage is obviously going to throw up loads of false positives. I get that they'd rather have false positives than false negatives, but it doesn't make it any less annoying. [1] https://github.com/JaviSoto/iOS7-Runtime-Headers/blob/master/PrivateFrameworks/PhotoLibraryServices.framework/PLManagedObjectContext.h https://github.com/JaviSoto/iOS7-Runtime-Headers/blob/master...