iPhone App Rejected for using "setMaxValue"

49 views
Skip to first unread message

enormego

unread,
Nov 17, 2009, 9:07:25 AM11/17/09
to ASIHTTPRequest
We had an app rejected for using private API calls, one of those calls
was setMaxValue. The only class I can find that's using setMaxValue is
ASIHTTPRequest, when it checks to see if it's NSProgressIndicator or
not. I'm not sure why this is causing an issue, but it might just be
better to just use "#if !TARGET_OS_IPHONE" than seeing if it responds
to the selector.

dotnetjunkie .

unread,
Nov 17, 2009, 9:15:18 AM11/17/09
to asihttp...@googlegroups.com
I have yet to go to the app store. I am curious though, how does the reviewers know you have used a private API call?

-Thanks.







> Date: Tue, 17 Nov 2009 06:07:25 -0800
> Subject: iPhone App Rejected for using "setMaxValue"
> From: shnh...@gmail.com
> To: asihttp...@googlegroups.com
> --
>
> You received this message because you are subscribed to the Google Groups "ASIHTTPRequest" group.
> To post to this group, send email to asihttp...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/asihttprequest?hl=.
>
>


Hotmail: Trusted email with powerful SPAM protection. Sign up now.

Ben Copsey

unread,
Nov 17, 2009, 9:16:56 AM11/17/09
to asihttp...@googlegroups.com
Argh, sorry about that.

I can't quite remember why I decided to do the detection at runtime, I guess it gives non-uiprogressview / nsprogressindicator delegates more flexibility. Anyway, I can't imagine too many people are using custom progress delegates on iPhone with the Mac-style progress API, so that sounds like a workable solution.

b

enormego

unread,
Nov 17, 2009, 9:17:13 AM11/17/09
to ASIHTTPRequest
All apps are now run through a "static analysis" that checks to see if
you're trying to call private methods

Ben Copsey

unread,
Nov 17, 2009, 10:04:50 AM11/17/09
to asihttp...@googlegroups.com
>> We had an app rejected for using private API calls, one of those calls
>> was setMaxValue. The only class I can find that's using setMaxValue is
>> ASIHTTPRequest, when it checks to see if it's NSProgressIndicator or
>> not. I'm not sure why this is causing an issue, but it might just be
>> better to just use "#if !TARGET_OS_IPHONE" than seeing if it responds
>> to the selector.


There's a fix in the latest version on GitHub now.

My apologies to anyone who gets hit by this.

Ben
Reply all
Reply to author
Forward
0 new messages