3 ms·

Apple systematically rejects apps that use private API's

• xuki 12y ago
  Only if you let them find out ;).
  • andyjohnson0 12y ago
    How would you prevent them from finding out?
    • xuki 12y ago
      https://speakerdeck.com/steipete/taking-advantage-of-the-runtime?slide=12 https://speakerdeck.com/steipete/taking-advantage-of-the-run... - see 2nd line Peter Steinberger (https://twitter.com/steipete https://twitter.com/steipete) shipped this in his PSPDFKit, which is used for Box/Dropbox/Evernote.
      • j_s 12y ago
        Here is the full video of that presentation: http://www.youtube.com/watch?v=frgnVhBcIFA http://www.youtube.com/watch?v=frgnVhBcIFA
  • logicallee 12y ago
    You're going to have to elaborate if you know any more, it seems incredibly easy to check programmatically.
  • nemasu 12y ago
    Hmmmmmm...downloadable 'modules'?
    • mantrax5 12y ago
      You can't download executable code to an iPhone app outside the App Store, only data.
      • nemasu 12y ago
        Curious, how do they know it's executable?
  • userbinator 12y ago
    Apps are Turing-complete, right? In theory, that means it's possible to make an arbitarily complex and obfuscated route to a private API, making it impossible to detect via simple static analysis.