5 ms·

This will be interesting indeed. "The Apple private frameworks have been removed from the iOS/watchOS/tvOS SDKs."

• cballard 11y ago
  What's the significance of this? Private things can be removed or modified at-will, seems fine?
  • tomschlick 11y ago
    Apps that are secretly using a private api (maybe not all the time to skirt the review process) might break, hard.
    • cballard 11y ago
      This is already the case for any OS update though, because that's a runtime dependency, not just a build-time dependency.
• earlz 11y ago
  Citation needed? I can't find any reference to this
  • axxl 11y ago
    It's in the the Xcode 7.3 release notes, which for some reason aren't loading for me. Here's a screenshot I took earlier however. http://i.imgur.com/oXAPsyd.png http://i.imgur.com/oXAPsyd.png
    • autoreleasepool 11y ago
      Very interesting. Apple has replicated f.lux's functionality and removed access to the key ingredient used in the authors original implementation. All in one felt swoop. They were definitely paying close attention to that whole "side load our proprietary blob using Xcode" debacle on HN 2 months ago. f.lux for iOS announcement: https://news.ycombinator.com/item?id=10544770 https://news.ycombinator.com/item?id=10544770 Apple's actions the next day: https://news.ycombinator.com/item?id=10556375 https://news.ycombinator.com/item?id=10556375
      • snuxoll 11y ago
        While it is a huge PITA, frameworks can still be reverse engineered - though not having headers makes it a lot harder.
        • comex 11y ago
          Private frameworks have never come with headers (on either OS X or iOS). This change only affects linking, and it only means that you have to create the .tbd files (just a list of available symbols) for ld to use manually - or use dlsym or other workarounds.
      • biot 11y ago
        It's "one fell swoop", unless you're swooping down on a billiards table, which is covered in felt.
        • autoreleasepool 11y ago
          Bah, I always screw that one up. I wrote that during my lunch break and it's too late to edit, but I appreciate the polite pedantry.
• ionforce 11y ago
  Anyone know what really popular apps would be affected by this?
  • autoreleasepool 11y ago
    Apps on the App Store can't use private API's so I'm assuming none.
    • josso 11y ago
      Not quite true. Apps aren’t allowed to use private API’s, but some apps still do.
      • autoreleasepool 11y ago
        If that's true, I'm very surprised they pass the App Store review considering how stringent the process is.
      • ionforce 11y ago
        Couldn't you just statically analyze the binaries to check for calls to barred functions?
        • prewett 11y ago
          No, because you can build a selector string at run-time and call that.
• Apocryphon 11y ago
  I wonder how this will affect the future of tools such as KIF - https://github.com/kif-framework/KIF https://github.com/kif-framework/KIF
  • pat2man 11y ago
    KIF could probably be rewritten to use the new UI testing framework.
    • Apocryphon 11y ago
      What additional functionality does KIF provide over XCUITest?
• bitserf 11y ago
  Apple removing these frameworks is a pretty strong signal that it's going to get harder/impossible to use in a future release. Probably not a reason to double down on your private API usage.
• hsshah 11y ago
  Can this impact Kodi side-loading in tvOS?! I don't know if it relies on any 'private framework'