Summary
China Android app stores rejected the app because the third-party SDK disclosure list is missing, incomplete, or inconsistent with the shipped app and policy.
China Android app stores App Review issue
SDK disclosure missing in China Android app stores
China Android app stores rejected the app because the third-party SDK disclosure list is missing, incomplete, or inconsistent with the shipped app and policy.
china android sdk disclosure missingchina app store sdk disclosurechina android rejection sdk disclosure
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
Major China Android app stores often expect a structured SDK vendor list, not just a generic sentence in the privacy policy.
Reviewers want vendor names, purposes, data categories, and sometimes permission mapping for each SDK.
This is a common failure point for global teams reusing a minimal western launch package.
Common causes
- No dedicated SDK disclosure table or store-specific artifact was prepared.
- The privacy policy names SDKs vaguely or omits China-relevant vendor and permission details.
- The shipped build contains push, login, ad, analytics, or payment SDKs that are not listed in the submission pack.
What the rejection often looks like
- The store asks for a complete third-party SDK list including vendor, purpose, collected personal information, and related permissions.
- Reviewers say the privacy policy mentions third-party services, but there is no separate SDK disclosure artifact or the current list is incomplete.
- The release is blocked because push, login, analytics, ad, or payment SDKs in the build are not fully disclosed in the submission package.
Step-by-step fix
- Step 1
Build a full SDK inventory that includes vendor name, purpose, personal information categories, and related permissions.
- Step 2
Update the Chinese privacy policy and store-facing declarations from that inventory.
- Step 3
Recheck the final build so the package reflects exactly what ships.
What to update
- SDK disclosure export for China Android app stores
- Chinese privacy policy vendor disclosure section
- Store submission attachments and declarations
- Release-specific SDK inventory
How to avoid getting rejected again
- Keep a release-specific SDK list instead of reusing a manually edited spreadsheet from a previous launch.
- Record vendor name, purpose, permissions, and privacy URL as soon as a new SDK is added to the project.
- Verify that regional Android builds and China-specific channels do not include extra SDK variants missing from the disclosure export.
How LogicSpring helps
- LogicSpring generates China-ready disclosure outputs from the same structured SDK inventory used for policy generation.
- Export workflows reduce manual spreadsheet work when stores ask for vendor-level detail.
- Precheck helps catch SDK and permission mismatches before resubmission.
FAQ
What does SDK disclosure in China Android app stores usually need to include?
Typically vendor name, SDK purpose, the types of personal information involved, related permissions, and often the vendor privacy policy URL. Some stores also expect the list to be separate from the main privacy policy.
Can I satisfy review in China Android app stores with only a privacy policy and no SDK list?
Often no. Many China Android app stores want a structured vendor-level disclosure artifact in addition to the privacy policy, especially when the app bundles push, login, analytics, advertising, or payment SDKs.
How is this different from App Store or Google Play disclosure work?
Review in China Android app stores is usually more explicit about vendor-level SDK lists and permission mapping. A western-style policy and console form set is often not enough on its own.