2.2 - Apps that exhibit bugs will be rejected
17.1 - Apps cannot transmit data about a user without obtaining the user's prior permission and providing the user with access to information about how and where the data will be used
2.2 Details
We discovered one or more bugs in your app when reviewed on iPad running iOS 9.2.1 and iPhone running iOS 9.2.1 on both Wi-Fi and cellular networks.
Specifically, the user account balance did not reflect properly upon purchasing the In-App Purchase products.
The steps to reproduce are:
1. Launch app
2. Navigate to Purchase/Recharge tab
3. Proceed to purchase one of the In App Purchase products
4. In App Purchase confirmation window appears
5. Confirm Purchase
6. User is prompted with Purchase Successful message
7. Balance does not reflect purchased content at the time of review
The review was conducted under sandbox environment.
Next Steps
Please run your app on a device to identify the issue(s), then revise and resubmit your app for review.
If we misunderstood the intended behavior of your app, please reply to this message in the Resolution Center to provide information on how these features were intended to work.
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce the issue(s). For updates, install the new version as an update to the previous version, then follow the steps to reproduce the issue(s).
Resources
--------------------------------------------------
17.1 Details
We noticed that your app does not obtain user consent or Privacy URL before collecting the user's personal data to 排行榜.
Next Steps
To collect personal data with your app, you must make it clear to the user that their personal data will be uploaded to your server and you must obtain the user's consent before the data is uploaded.
- Starting with iOS 6, there are keys for specifying the reason the app will access the user's protected data. When the access prompt is displayed, the purpose specified in these keys is displayed in that dialog box. If your application will be transmitting protected user data, the usage string in your access request should clearly inform the user that their data will be uploaded to your server if they consent.
Resources
For more information on these keys, please see the Information Property List Key Reference.
If you have difficulty reproducing a reported issue, please try testing the workflow described in Technical Q&A QA1764: How to reproduce bugs reported against App Store submissions.
If you have code-level questions after utilizing the above resources, you may wish to consult with Apple Developer Technical Support. When the DTS engineer follows up with you, please be ready to provide:
- complete details of your rejection issue(s)
- screenshots
- steps to reproduce the issue(s)
- symbolicated crash logs - if your issue results in a crash log
17.1 - Apps cannot transmit data about a user without obtaining the user's prior permission and providing the user with access to information about how and where the data will be used
2.2 Details
We discovered one or more bugs in your app when reviewed on iPad running iOS 9.2.1 and iPhone running iOS 9.2.1 on both Wi-Fi and cellular networks.
Specifically, the user account balance did not reflect properly upon purchasing the In-App Purchase products.
The steps to reproduce are:
1. Launch app
2. Navigate to Purchase/Recharge tab
3. Proceed to purchase one of the In App Purchase products
4. In App Purchase confirmation window appears
5. Confirm Purchase
6. User is prompted with Purchase Successful message
7. Balance does not reflect purchased content at the time of review
The review was conducted under sandbox environment.
Next Steps
Please run your app on a device to identify the issue(s), then revise and resubmit your app for review.
If we misunderstood the intended behavior of your app, please reply to this message in the Resolution Center to provide information on how these features were intended to work.
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce the issue(s). For updates, install the new version as an update to the previous version, then follow the steps to reproduce the issue(s).
Resources
--------------------------------------------------
17.1 Details
We noticed that your app does not obtain user consent or Privacy URL before collecting the user's personal data to 排行榜.
Next Steps
To collect personal data with your app, you must make it clear to the user that their personal data will be uploaded to your server and you must obtain the user's consent before the data is uploaded.
- Starting with iOS 6, there are keys for specifying the reason the app will access the user's protected data. When the access prompt is displayed, the purpose specified in these keys is displayed in that dialog box. If your application will be transmitting protected user data, the usage string in your access request should clearly inform the user that their data will be uploaded to your server if they consent.
Resources
For more information on these keys, please see the Information Property List Key Reference.
If you have difficulty reproducing a reported issue, please try testing the workflow described in Technical Q&A QA1764: How to reproduce bugs reported against App Store submissions.
If you have code-level questions after utilizing the above resources, you may wish to consult with Apple Developer Technical Support. When the DTS engineer follows up with you, please be ready to provide:
- complete details of your rejection issue(s)
- screenshots
- steps to reproduce the issue(s)
- symbolicated crash logs - if your issue results in a crash log
扫一扫
4万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
