Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

showing an update dialog in iOS #927

Closed
kelset opened this issue Jul 18, 2017 · 5 comments
Closed

showing an update dialog in iOS #927

kelset opened this issue Jul 18, 2017 · 5 comments
Labels

Comments

@kelset
Copy link
Contributor

kelset commented Jul 18, 2017

In the Plugin Usage section of the README, the very last paragraph says:

NOTE: While Apple's developer agreement fully allows performing over-the-air updates of JavaScript and assets (which is what enables CodePush!), it is against their policy for an app to display an update prompt. Because of this, we recommend that App Store-distributed apps don't enable the updateDialog option when calling sync, whereas Google Play and internally distributed apps (e.g. Enterprise, Fabric, HockeyApp) can choose to enable/customize it.

I've been going through the Apple Developer Program License Agreement, which can be downloaded from this page, but I couldn't find any rule around not showing/presenting the user with an Alert / a UI element to tell him/her to update the app to the latest version.

Moreover, the only instance of "not allowance" I could find was an Ionic app back in January and lately apps like Ryanair and Monzo have adopted a similar behaviour (showing a full page "alert" to tell you to update).

Can it be that maybe now this "interaction" is not disallowed anymore?

Even the "mighty" paragraph 3.3.2 has been updated to be more "open" to OTA installations:

Interpreted code may be downloaded to an Application but only so long as such code: (a) does not change the primary purpose of the Application by providing features or functionality that are inconsistent with the intended and advertised purpose of the Application as submitted to the App Store, (b) does not create a store or storefront for other code or applications, and (c) does not bypass signing, sandbox, or other security features of the OS.

(version 20170605)

Do you have any more "precise" information around this issue? Or should the README be updated to not disincentivizes the update dialog?

@kelset kelset changed the title showing an update dialog in iOS [question] showing an update dialog in iOS Jul 18, 2017
@max-mironov
Copy link
Contributor

Hello @kelset, thank you for your question.

So while there is actually no strict rule and 100% guarantee that the app will be banned this way users should be aware of the following statement (taken from AppStore Review Guidance):

Apps must not force users to rate the app, review the app, download other apps, or other similar actions in order to access functionality, content, or use of the app.

That's the thing that should be taken into account while using the update dialog with iOS.

@kelset
Copy link
Contributor Author

kelset commented Jul 18, 2017

Hey @max-mironov, thanks for pointing out that extract, didn't read that document.
I guess that, then, there is probably a fine line there of showing something without "forcing" and still allowing the user to keep using the app in the standard way.

(I think that we can close the issue then, maybe I can submit a small PR to have all these information in the README)

@kelset kelset closed this as completed Jul 18, 2017
@max-mironov
Copy link
Contributor

@kelset gotcha, if you could create a PR to improve the existing documentation that would be much appreciated.

kelset added a commit to kelset/react-native-code-push that referenced this issue Jul 22, 2017
Related to issue microsoft#927, my take on expanding the section that mentions Apple's ruling over OTA updates & update promts.
patniko pushed a commit that referenced this issue Jul 24, 2017
* Clarify store rulings

Related to issue #927, my take on expanding the section that mentions Apple's ruling over OTA updates & update promts.

* Update README.md

Cleaned up verbiage and section header.
@christophmegusta
Copy link

i think this ticket is not yet completely done as this doc still shows the old paragraph
https://github.com/Microsoft/cordova-plugin-code-push#plugin-usage

maybe only the react native project got the change yet?

@kelset
Copy link
Contributor Author

kelset commented Jun 15, 2018

@christophmegusta that's another repo, I've submitted a PR to this one.

yeomann added a commit to yeomann/appcenter-docs that referenced this issue Jul 26, 2018
Related to issue microsoft/react-native-code-push#927 
as it seems docs are kinda scattered and appcenter-docs seems to be go to follow for CodePush. Thus this PR added missing info from `react-native-code-push` readme. 


Ref to Original PR: https://github.com/Microsoft/react-native-code-push/pull/936/files
jwargo pushed a commit to MicrosoftDocs/appcenter-docs that referenced this issue Jul 26, 2018
Related to issue microsoft/react-native-code-push#927 
as it seems docs are kinda scattered and appcenter-docs seems to be go to follow for CodePush. Thus this PR added missing info from `react-native-code-push` readme. 


Ref to Original PR: https://github.com/Microsoft/react-native-code-push/pull/936/files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants