Detecting the use of private APIs?

Discussion in 'iOS Programming' started by FloatingBones, Sep 14, 2011.

  1. FloatingBones macrumors 65816

    FloatingBones

    Joined:
    Jul 19, 2006
    #1
    According to this blog entry, there were a group of WiFi-scanning apps pulled in early 2010 from the App store. There is a quote apparently from Apple noted in that article:

    "There are no published APIs that provide the ability to manipulate the wireless connection or the show level of information regarding the wireless connection as demonstrated in the application."

    Is there a technical reason why Apple can't scan submitted apps to detect the use of private APIs? Have they modified their procedure in the last year to catch private APIs as part of the approval process?
     
  2. robbieduncan Moderator emeritus

    robbieduncan

    Joined:
    Jul 24, 2002
    Location:
    London
    #2
    They auto-scan now. I had an app update rejected as I used a private API to terminate the app if some internal resources had somehow got corrupted (I simply removed that functionality).
     
  3. ianray macrumors 6502

    Joined:
    Jun 22, 2010
    Location:
    @
    #3
    A scan is also run when submitting an App to iTunes Connect.
     
  4. FloatingBones thread starter macrumors 65816

    FloatingBones

    Joined:
    Jul 19, 2006
    #4
    Thanks for the response, Robbie. Just so I am perfectly clear: at some point in the past, Apple didn't scan. Today, they scan submitted apps for private APIs. Do I understand correctly? Do you recall if this was something announced on the MR front page when they made the change, or was it a more silent event?
     
  5. firewood macrumors 604

    Joined:
    Jul 29, 2003
    Location:
    Silicon Valley
    #5
    Silent change. Developers just started reporting rejections for stuff they'd had accepted before. Apple seems to catch on (and silently change their inspection procedures) any time enough devs try to sneak around some guideline.
     
  6. FloatingBones thread starter macrumors 65816

    FloatingBones

    Joined:
    Jul 19, 2006
    #6
    Thanks @firewood. This sounds like a good change. If apps are pulled after being listed in the App Store, that tends to drag customers into the issue and can give Apple a little PR problem.
     
  7. PhoneyDeveloper macrumors 68030

    PhoneyDeveloper

    Joined:
    Sep 2, 2008
    #7
    It's probably the case that they scanned from an early time but that what they scanned for has changed over time. I had an app rejected for a private api where the app had previously been accepted with use of the same api. This was in piracy detection code and I had no choice but to remove it. In the past they only scanned after you submitted the app. Today the scan happens when you use the validate button in the Organizer window as well as after you submit.
     

Share This Page