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

[BUG]Violation of Apple Store Review Guidelines #316

Closed
1 of 3 tasks
nexussmart opened this issue Jul 23, 2018 · 1 comment
Closed
1 of 3 tasks

[BUG]Violation of Apple Store Review Guidelines #316

nexussmart opened this issue Jul 23, 2018 · 1 comment

Comments

@nexussmart
Copy link

nexussmart commented Jul 23, 2018

I'm submitting a ... (check one with "x"):

  • bug report
  • feature request
  • documentation issue

Bug report

Current behavior:

Any ios app build with the plugin can be reject at submission on the Apple Store.

Actual rejection from an app with following review:

Guideline 2.5.1 - Performance - Software Requirements

Your app uses the "prefs:root=" non-public URL scheme, which is a private entity. The use of non-public APIs is not permitted on the App Store because it can lead to a poor user experience should these APIs change.

Continuing to use or conceal non-public APIs in future submissions of this app may result in the termination of your Apple Developer account, as well as removal of all associated apps from the App Store.

Next Steps

To resolve this issue, please revise your app to provide the associated functionality using public APIs or remove the functionality using the "prefs:root" or "App-Prefs:root" URL scheme.

Related code:

I found these references in the src/ios/Diagnostic.m file @345 and @347:

#if __IPHONE_OS_VERSION_MAX_ALLOWED <= __IPHONE_8_0
url = [NSURL URLWithString: @"prefs:root=LOCATION_SERVICES"];
#else
url = [NSURL URLWithString: @"App-Prefs:root=Privacy&path=LOCATION"];
#endif

@nexussmart nexussmart changed the title Violation of Apple Store Review Guidelines [BUG]Violation of Apple Store Review Guidelines Jul 23, 2018
@dpa99c
Copy link
Owner

dpa99c commented Jul 24, 2018

Duplicate of #262

Note: the code causing this issue was removed by this commit so is no longer present in the plugin; you can confirm this by searching the plugin source for the offending prefs:root and see that it is no longer present.

So please update to the latest version of the plugin to resolve this.

@dpa99c dpa99c closed this as completed Jul 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants