-
Notifications
You must be signed in to change notification settings - Fork 40
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
App Rejection with This Framework #10
Comments
Hi, Could you please let me know what version of the SDK do you use? (VERSION.MD file) |
I'm using 2.9.1 |
I have pushed an update with iBeacons completely removed (all the iBeacons function are just empty stubs). I hope this would help! |
My app was accepted to AppStore. I have used PushWoosh version 2.9.4. |
That's a good news! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Three of my apps with the Pushwoosh Framework have been rejected because of the use of iBeacon by the Pushwoosh Framework.. grr.. after waiting 13 days for the review.. Below is the response from Apple. I figured out that only PushWoosh has references to iBeacon in my app, by using the strings command (see below).. I don't have the location value added to the UIBackgroundModes key.. Please fix this, I want to get my apps approved, but I don't want to have PushWoosh removed!!
strings -a Pushwoosh | grep -e 'CLBeaconRegion' CLBeaconRegion.h v40@0:8@"CLLocationManager"16@"NSArray"24@"CLBeaconRegion"32 v40@0:8@"CLLocationManager"16@"CLBeaconRegion"24@"NSError"32 CLBeaconRegion.h CLBeaconRegion @"CLBeaconRegion"
PLA 3.3.1
Additionally, we found that your app uses iBeacons APIs, but does not include iBeacon functionality within the app.
Using these APIs in an unapproved manner is not in compliance with the iOS Developer Program License Agreement, as required by the App Store Review Guidelines.
In particular, section 3.3.1 of the iOS Developer Program License Agreement specifies:
"Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs"
If there are no alternatives for providing the functionality your app requires, we encourage you to file an enhancement request or to work with the Apple Developer Technical Support team to explore alternative solutions.
The text was updated successfully, but these errors were encountered: