Skip to main content

Information We Need From You

To get started, please provide the following information as completely and accurately as possible. Missing or incomplete information may result in delays during setup, testing, or app submission.

Not sure what to gather?

Start with the Preparation Checklist to see everything you need before submitting.

1) App identifiers (Bundle IDs)​

For each iOS app you plan to distribute, please provide:

  • Desired Bundle ID (example: com.yourcompany.yourapp)
  • App name, as it should appear in App Store Connect
  • List of required app capabilities, such as (but not limited to):
    • Push Notifications
    • In-App Purchases
    • Sign in with Apple
    • Associated Domains
    • App Groups
Capabilities must be listed upfront

Adding or changing capabilities after setup may require updating the App Identifier and regenerating provisioning profiles.

Global availability (App Store Connect)

Please confirm whether this app is already listed globally on the App Store under your own Apple Developer account.

If the same app is already available internationally, Apple may flag the China-specific version as a duplicate submission (Guideline 4.3(a)). We have two standard solutions:

  • Exclude Mainland China from your global App Store listing, or
  • Provide an authorization letter stating AppInChina is permitted to submit the app in China on your behalf

See also: App Review Guideline 4.3(a): Duplicate App Rejection.

Submit this early

We cannot proceed with creating App Identifiers, provisioning profiles, or initiating required filings until your Bundle ID and capabilities are confirmed.

If the chosen Bundle ID is unavailable and we are forced to change it after filings have started, we may need to redo registrations such as:

  • Mobile App Filing (备案)
  • Software Copyright Certificate
  • ICP registration
  • User-facing documents (privacy policies, terms of service, etc.)

We strongly recommend confirming your desired Bundle ID with us before we begin any filing procedures. We can check and reserve your proposed Bundle ID in our Apple Developer account before proceeding.

2) Provisioning profiles​

For each provisioning profile you require, specify:

  • Associated Bundle ID (must exactly match the App Identifier)
  • Profile type:
    • Development: internal testing and debugging on registered devices
    • Distribution: App Store release or other distribution methods
  • Target usage (local development, CI/CD builds, TestFlight, etc.)
  • Device UDIDs (required only for development profiles)

Provisioning profiles are generated and managed by AppInChina. Any change to certificates, devices, or app capabilities may require profiles to be regenerated.

3) Test devices (development profiles only)​

Test devices are required only for development provisioning profiles.

Due to Apple’s annual device registration limits, test devices are capped per device type and cannot be removed once registered for the current membership year.

Per app, the default limits are:

  • iPhone: up to 3 devices
  • iPad: up to 3 devices

Additional devices may be approved subject to availability and with appropriate technical or business justification. Approval is not guaranteed.

For each test device, please provide:

  • Device name (example: “John’s iPhone 14”)
  • UDID (Unique Device Identifier)

4) App Store Connect access​

At least one member of your team must have access to App Store Connect to manage app metadata, monitor review status, respond to Apple inquiries, and handle compliance-related requests.

Access prerequisites (avoid onboarding delays)

Before you request access, confirm each team member:

  • Has an active Apple ID they can sign into
  • Has two-factor authentication (2FA) enabled and access to the trusted device/phone number
  • Can receive and accept Apple email invitations promptly

For each user who requires access, please provide:

  • Full name
  • Email address (must match the email associated with the user’s Apple ID)
  • Requested role (example: App Manager, Developer, Marketing)
  • Brief description of responsibilities

Important notes:

  • The highest level of access we can grant is App Manager.
  • If you are responsible for uploading builds with Apple Transporter, request App Manager access.
  • Please follow the principle of least privilege and request only the permissions strictly necessary.
  • Each user must accept the invitation sent by Apple to activate their access.

5) App Groups and additional identifiers (if applicable)​

If your app requires additional Apple identifiers, please provide details:

  • For App Groups:
    • Desired App Group name (example: group.com.yourcompany.yourapp)
    • Apps and provisioning profiles that should be associated with the App Group
    • Purpose (example: shared storage, app extension communication)
  • For embedded extensions or widgets:
    • Bundle ID for each embedded target (example: com.yourcompany.yourapp.todayextension)
    • Component name (example: “Today Widget”, “Watch Extension”)
    • Whether it is intended to be a standalone app in App Store Connect (Yes/No)
Placeholder app records to reduce cross-client visibility

In our shared Apple Developer / App Store Connect organization, identifiers like Bundle IDs (including internal-only targets such as widgets or extensions) can appear in dropdowns and selectors.

To reduce accidental exposure, we can create placeholder app records for internal-only Bundle IDs so that:

  • The identifier is removed from “available identifiers” dropdowns shown to other clients
  • We reduce the chance of accidental discovery during setup workflows
  • We prevent accidental reuse of identifiers

These placeholder apps are not published and contain no metadata or assets.

Important: please review the disclosure in iOS App Distribution (Overview) about cross-client visibility in shared App Store Connect organizations.

For other identifiers (such as Merchant IDs), include:

  • Identifier type
  • Desired name/format (if applicable)
  • Purpose and integration details

6) Push notifications (APNs)​

If your app uses Apple Push Notification service (APNs):

  • Clients always send push notifications from their own backend systems
  • AppInChina manages all APNs configuration within the Apple Developer Account
  • We use certificate-based APNs authentication in our shared account environment

For each app with push notifications enabled, AppInChina will securely provide:

  • APNs SSL certificate (.cer)
  • APNs private key bundle (.p12)

APNs Auth Keys (.p8) are not used or shared in our shared Apple Developer account setup.

If your app requires special push notification types (background notifications, VoIP pushes, Live Activities), inform us upfront so we can configure the App Identifier and provisioning profiles accordingly.