5 ms·

Worst of all, not even attempt to hide it. It is very easy to hide such trivial uses of "private" API.

• masklinn 11y ago
  I'd say attempting to hide it would be way worse, it would have been better if they'd clearly noted they're making use of private APIs which could break at any moment in the readme/documentation, but at least you can see it's dodgy by just going through the code.
  • LeoNatan25 11y ago
    The way I see it, there are two types of private API use - malign and benign. Malign would be attempting to circumvent iOS security, such as attempting to access disallowed services, attempting to retrieve personal information, abuse, etc. Bening would be use for overcoming Apple bugs or shortcomings in public API. If for the latter, as here, it is not that bad in my book.
    • masklinn 11y ago
      Motivation is irrelevant to my comment. If you're using private APIs in a library, any user of the library is at risk of submission rejection because of the library, the least you can do for them is let them make an at least somewhat informed choice about it, and ideally (if your library is multi-purpose) have them opt in the behaviour requiring private API access. It's not a question of purpose or of "badness", and really has nothing to do with your book.
      • LeoNatan25 11y ago
        Oh, I agree with that completely. Just wanted to distinct between "good" and "bad" use of private API.