Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion PhoneGap app rejected by Apple for using "private API"
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
J. Matthew Pryor  
View profile  
 More options May 19 2009, 7:09 pm
From: "J. Matthew Pryor" <j.matthew.pr...@gmail.com>
Date: Wed, 20 May 2009 09:09:35 +1000
Local: Tues, May 19 2009 7:09 pm
Subject: Re: [PhoneGap] Re: PhoneGap app rejected by Apple for using "private API"

[[Ajaxian thread readers please excuse the cross-post]]

Forgive my lack of understanding but how it is any different that a PhoneGap
based app could use a UIWebView to download dynamic content that any of the
huge number of existing apps in the AppStore that clearly do the same thing?
This is not an attempt to understand Apple's policy, its really a technical
question. What additional vulnerabilities or unwanted surprises would/could
a PhoneGap based app expose a user to that any Objective-C based app that
used UIWebView didn't?
I use the ABC (Australia) app regularly which clearly downloads dynamic
content in to a custom UI (not mobile Safari), and I assume that this
content could include Javascript. Is it the fact that PhoneGap exposes
native API to JS that creates the problem?
I feel it would be better to take the "you should have known/that's the way
it is" element out of this discussion and move it to a rational technical
conversation about what PhoneGap can & can't do & stay within a reasonably
unambiguous interpretation of the AppStore listing rules.
Constructive & detailed technical input seems a far more valid contribution
to the debate at this stage.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.