Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
In news that surprises no one, if you do things that Apple clearly states in the terms that you can not do (use private frameworks) your app will be rejected. If this thread where about something in a gray area that'd be one thing...but these guys should have known before they even finished downloading the official SDK that their app would be rejected.
 
So Apple doesn't allow this great, and extremely useful app, but allows the Google app to do contact search?

Great double standards there. I guess if Polar Bear had someone on the Board of Apple they'd get their app approved.
 
So Apple doesn't allow this great, and extremely useful app, but allows the Google app to do contact search?

Great double standards there. I guess if Polar Bear had someone on the Board of Apple they'd get their app approved.
Does the contacts search use private frameworks?

This app knowingly violates the terms, the DECLARED ones. But i cant wait for this to turn into yet another "zomg apples worse than the nazis!" thread just like the last one.
 
In news that surprises no one, if you do things that Apple clearly states in the terms that you can not do (use private frameworks) your app will be rejected. If this thread where about something in a gray area that'd be one thing...but these guys should have known before they even finished downloading the official SDK that their app would be rejected.

Actually that's incorrect. We carefully developed Search to be fully compliant with the iPhone SDK Agreement to the letter. It did NOT use any private API's. Although that was Apple's initial justification for the rejection, we pointed out that that was incorrect, and in our subsequent discussions Apple conceded that that was correct, and we were not using any private API's to add this functionality.

Layton Duncan
Polar Bear Farm Ltd
 
Does the contacts search use private frameworks?

This app knowingly violates the terms, the DECLARED ones. But i cant wait for this to turn into yet another "zomg apples worse than the nazis!" thread just like the last one.

Incorrect. It does not violate the iPhone SDK Agreement. See above.
 
Does the contacts search use private frameworks?

This app knowingly violates the terms, the DECLARED ones. But i cant wait for this to turn into yet another "zomg apples worse than the nazis!" thread just like the last one.

**EDIT** Scrap all that: "I didn't read about the private frameworks - if it has broken these rules, then yep. It should have known better!" **EDIT**

So it is double standards from Apple then?
 
So what's the problem with your Application ?
WE REALLY NEED SEARCH FUNCTION IN CALENDAR APPLICATION AN NOW THAT A GOOD PROGRAMMER FILLS THIS LACK APPLE REJECT IT !
IT'S TOTAllY INACCEPTABLE!!
 
Actually that's incorrect. We carefully developed Search to be fully compliant with the iPhone SDK Agreement to the letter. It did NOT use any private API's. Although that was Apple's initial justification for the rejection, we pointed out that that was incorrect, and in our subsequent discussions Apple conceded that that was correct, and we were not using any private API's to add this functionality.

Layton Duncan
Polar Bear Farm Ltd

Interesting, I stand corrected. When I was at WWDC there were several questions about accessing the calender and the response was "it's not allowed". I'm assuming that even though you found a technical way around that restriction Apple still felt that it violated the spirit of the restriction (as BS as the restriction is).
 
for teh luvvaGawd clarify!

pleasing to tell a dummy like m3 what a 'private' framework is.

to add sounds I have to add the 'audio.toolbox.framework'. to add tables i have to use the 'core.graphics.framework'.

Are these private? where can I empirical evidence??

cheers.bo

:apple:<= does this site have the rights to use this logo?
 
And now Apple won't even let you share your rejection letter due to the NDA, so we all better stop talking about it before we get sued! :D
 
what do you mean you didnt violate the SDK? It clearly says that access to the calendar is NOT allowed. Just because you said didn't use private header doesn't mean you didnt violate the SDK if you are going directly against their intension.
 
Do you have read the sdk ?
It clearly states that calendar access is now allowed ?
Also for ONLY reading data (reading cannot destroy anything, isn't it ?).
Why searching for contacts is allowed ?
Why Apple not enabled searching calendar capabiities ?
Why ?
 
Do you have read the sdk ?
It clearly states that calendar access is now allowed ?
Also for ONLY reading data (reading cannot destroy anything, isn't it ?).
Why searching for contacts is allowed ?
Why Apple not enabled searching calendar capabiities ?
Why ?

no, calendar access is NOT allowed
 
It clearly says that access to the calendar is NOT allowed.
Actually it doesn't state that at all, far from it, not even Apple believes that. Unfortunately I can't really comment further on that at this point.

Anyway, while we are disappointed Search could not be approved in it's intended form, we tried our utmost to get it approved. In the end it's Apple's choice as to what they accept or decline for the App Store. We've voiced our opinions, suggestions, and concerns to ALL levels within Apple a few weeks ago. This included many aspects relating to iPhone development. Seems other high profile, long standing Mac developers are starting to do so too. I just hope some clarity comes out of this... and quickly!

Layton Duncan
Polar Bear Farm Ltd
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.