If you author code to do that, then yes, you could send contacts to a server.
> 2) I see that PhoneGap has an unimplemented class called File. Will
> that be a security hole when implemented?
No. The concept is to provide a sandboxed api to fit w/ the sdk terms.
That's my thought too ... though of course the rebuttal is that Apple
has the ability to scan for that if they chose.
But the point is the same, anything that has access to both the
network *and* the Phone internals is a vector for attack. PhoneGap
isn't any different than someone writing this ability into an ad-hoc
ObjC (or Java for those of us with Android!) program.
-Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "phonegap" group.
To post to this group, send email to phon...@googlegroups.com
To unsubscribe from this group, send email to
phonegap+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/phonegap?hl=en?hl=enFor more info on PhoneGap or to download the code go to www.phonegap.com
-~----------~----~----~----~------~----~------~--~---
Apple's official stance is documented in its terms of service, which
are available to all of us equally. The problem is with a particular
reviewer's interpretation of those terms.
> ...
> don't make the decisions, but to the degree I'm advising them, if there's
> uncertainty with getting into the App Store if using PhoneGap, be it an
> occasional rejection (even if there are other apps in the store), I cannot
> recommend PhoneGap as a direction for significant business investment
> without knowing for sure that PhoneGap isn't a potential obstacle.
Nothing in life is for sure, especially when it involves human beings
and their opinions.
Paul Prescod
-Peter
Hello Peter,
Upon review of your application, Free for All Mas cannot be posted to
the App Store due to the usage of private API. Usage of such
non-public API, as outlined in the iPhone SDK Agreement section 3.3.2
is prohibited:
" An Application may not itself install or launch other executable
code by any means, including without limitation through use of a
plug-in architecture, calling other frameworks, other APIs or
otherwise. No interpreted code may be downloaded and used in an
Application except for code that is interpreted and run by Apple's
Published APIs and built-in interpreter(s).
The PhoneGap API implemented in your application is an external framework.
my programming is meant to feed my family
What is clear is that Apple does not want "dynamic" apps.
So if you see they have started lookign into it adn they dont like applications that use loading safari adn runngn teh entire app
I submitted the first update to iBlipper last Friday. It's from a
recent nachoman build with the unphonegap.py script run.
The app makes one outbound call per run to an "update.js" file on my
server -- I'm just using it to get usage logs currently.
Now, the new build mechanism means that I do have a phonegap.js file
but other references should be gone. I'll let ya'll know when I get a
response.
_A
BTW, has anyone heard of other frameworks like QuickConnect or Rhodes
having problems?
or until they discover you fool Apple too much then Apple might ban
your account instead.
I do use phonegap in my app and also has email about it. And also
thank you for PhoneGap that already provided that opportunity.
At the same time, this directly related to time and money investment
in creating the app using phonegap, I don't think it is fear-
mongering. What I am trying to do, is to bring awareness that this
might possibly a bigger priority. Sometimes, we might think all we
need is just to create a good framework however there is the other end
of business/legal side that we need to deal with.
Sorry, if my message cause fear-mongering. I will keep quite about it
then and put it in the back burner.