Summary
The store requires a third-party SDK list with vendor-level detail, and the app's current submission pack does not meet that requirement.
China Android app stores App Review issue
Third-party SDK list requirement in China Android app stores
The store requires a third-party SDK list with vendor-level detail, and the app's current submission pack does not meet that requirement.
china android third party sdk listchina sdk list requirementthird party sdk list china app store
Fix China Android app stores review issues before the next submission
Use LogicSpring to run a free precheck, regenerate the right policy or disclosure pack, and shorten the loop from rejection notice to resubmission.
What this means
Many China Android app stores expect a separate structured vendor list beyond the main privacy policy.
This list often includes SDK purpose, collected data, permission use, and links to vendor privacy notices.
Global teams commonly miss this because western store workflows do not always require the same level of SDK granularity.
Common causes
- The submission includes only a privacy policy and no separate SDK list.
- Vendor names, collected fields, or permissions are incomplete.
- The list was created manually and no longer matches the release build.
Step-by-step fix
- Step 1
Generate a release-specific SDK list from the actual dependency inventory.
- Step 2
Include vendor name, purpose, personal information categories, permissions, and policy links where required.
- Step 3
Keep the SDK list versioned alongside the release so future updates do not reuse stale vendor information.
What to update
- Third-party SDK list
- Vendor privacy references
- Chinese Privacy Policy
- Submission attachments
How LogicSpring helps
- LogicSpring generates structured China-facing SDK outputs from one inventory instead of ad hoc spreadsheets.
- The same data can then feed policy generation and store-specific exports.
- This makes it practical to scale from one China store to many without rewriting disclosures each time.
FAQ
Can I resubmit to China Android app stores without changing the binary?
Only for pure listing or form corrections. If the shipped build still requests the wrong permission, bundles the wrong SDK, or behaves inconsistently, resubmitting the same build is risky.
What evidence should I prepare before resubmitting?
Prepare the updated public policy URL, the exact store fields you changed, screenshots for permission or disclosure flows where relevant, and a short reviewer note explaining what changed and why it now matches the app.
Should the privacy policy, store form, and in-app disclosure all match?
Yes. Review teams compare these surfaces together. If one says you collect or disclose something and another says you do not, the mismatch itself often becomes the next rejection.