Clarifying 1 thing.
PhoneGap apps have definitely been rejected under 2.5.2, but not because of
their use of , in the case of the PhoneGap
Developer app it was because it could, and did load arbitrary other (user
entered) apps by url alone. Something Apple thinks of as an attempt to
create your
Also, please keep in mind that there are other ways to distribute apps.
A company/developer with an enterprise license can build apps for
company/employee use and distribute them as they see fit.
On Tue, Oct 22, 2019 at 9:20 AM Jesse wrote:
> This is a crucial feature for development tools,
I have not tested, but supposedly you can point to a local html error file.
Whenever a navigation error occurs, it should navigate to that local page.
Anyway, I see no point in limiting the content tag, people can still
navigate to remote sites by using javascript as long as the remote url is
This is a crucial feature for development tools, and a valid production use
case.
1. This is NOT breaking TOS with Apple, unless the developer decides to
significantly change their app, which is bad practice anyway.
2. Care should be taken in what you deliver to your app, this is not
cordova's
There are some things I definitely disagree with in your list of
responses. I do think
the enterprise setup is enough of a reason to not add any kind of
deprecation notice as I originally proposed. So I concede on the idea of
deprecating this usage of the feature.
I however do still think, a
This is an extension of the issue I raised for adding warnings to the
documentation which can be found at
https://github.com/apache/cordova-docs/issues/1022
In my opinion there are several reasons why using a remote url (such as
https://myserver.com/) to host a cordova app is bad practice.
The content tag is also used for pointing to local development servers and
benefit from live reloading, so how do you plan to deprecate it only for
remote urls?
El mar., 22 oct. 2019 a las 17:46, Norman Breau ()
escribió:
> This is an extension of the issue I raised for adding warnings to the
>
Good point julio. Local development for live reloading is a valid reason
to use remote urls. I still think it's not valid
if the --release flag is present. So my initial reaction is to allow
usage while in debug mode, by disallow in release mode.
Or at very least provide a scary warning if a
Yes, I've conceded on the proposal of limiting the behavior. You two
made some good points on why the behavior should be left alone.
I've kind of adjusted my position to instead document how it's bad
practice to use remote URLs for index/sources because while allowing
remote code is still
Yes, it can be risky in an app store, but to date, there have been no
reports to cordova or phonegap of apps being rejected under this clause.
Apple's goal, I believe, is primarily to stop the 'app store in an app' and
apps that significantly change their behavior without going through the
review
Nightly build #1210 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/1210/consoleFull
-
Jenkins for Apache Cordova
11 matches
Mail list logo
