iOS IAP Review Submission Mapper

Get a structured English-by-default resubmission checklist for one specific problem: an in-app purchase or subscription was not included with the app-version review submission.

The result separates what you reported from what still needs evidence, then maps the issue to official Apple guidance, verification steps, blockers, and conditional English Review reply points. Choose full English output or Korean guidance with English reply skeletons. It is not a free-text classifier and does not read App Store Connect.

Price: US$19 for one successfully stored structured map. Platform usage is included. Starting another run can produce another charge.

Use this Actor when

• the App Review issue is specifically that an IAP or subscription was not included with the app-version submission;
• you want a deterministic checklist rather than pasting a rejection message into a general-purpose model;
• you can verify the final App Store Connect state yourself before resubmitting.

Do not run it for purchase-button failures, subscription-disclosure issues, other review guidelines, or a request for approval prediction.

Supported input

The Actor accepts predefined selections only:

• platform: ios
• appType: iap or subscription
• issueType: iap-not-in-review-submission
• optional outputLanguage: en or ko; omitted input defaults to English
• optional predefined deviceFamily
• optional predefined checkedActions

Unknown fields and values are rejected with one generic error. Do not enter rejection text, names, email addresses, app or product identifiers, submission identifiers, URLs, paths, tokens, or arbitrary notes.

Dummy input: examples/dummy_input.json

Valid JSON example:

{
  "platform": "ios",
  "appType": "iap",
  "issueType": "iap-not-in-review-submission",
  "outputLanguage": "en",
  "deviceFamily": "not provided"
}

Result

The Actor stores one result item in the run's default dataset. The result contains:

• Apple App Review Guideline 2.1(b) and the official IAP submission procedure
• facts separated from unverified hypotheses
• actions and evidence for metadata, review screenshots, version linkage, agreements/tax/banking, and sandbox lookup
• one explicit status for every predefined check
• conditional reply skeletons that require supporting evidence before any completion statement
• blockers that prevent a truthful completion claim

Safe enum selections are deliberately reflected in the result and marked with selectionValuesReflected: true. User-reported checks remain unverified.

The default en result returns the complete narrative and Markdown report in English. Selecting ko preserves Korean guidance while keeping App Review reply skeletons in English. Machine-readable field names, enum values, and status codes stay stable in both modes.

Example of the result structure:

{
  "privacy": "structured-no-free-text",
  "outputLanguage": "en",
  "semanticReviewRequired": true,
  "checkStatuses": [
    {
      "code": "iap-metadata-complete",
      "status": "not-provided-not-evidence-of-nonperformance"
    }
  ],
  "issues": [
    {
      "classification": "apple-2.1b-iap-submission",
      "guideline": "2.1(b)",
      "actions": ["..."],
      "evidence": ["..."],
      "blockers": ["..."]
    }
  ]
}

Pricing

The Actor requests the custom analysis-report event only when it writes the structured result to the default dataset. Rejected input and generation failures before that write do not call the charge event. The event is configured as one-time per run, so an in-run retry cannot charge it twice. A separate run can trigger a separate US$19 charge.

Privacy and storage

• The Actor accepts no arbitrary text fields and does not log input values.
• Results use privacy: structured-no-free-text and inputEchoed: false.
• Apify may retain Actor input, run records, logs, and storage under its platform and account-plan policies. This Actor does not promise no-store behavior.
• A run or an Actor issue attachment can broaden access. Inspect a run before sharing it.
• The Actor needs no Apple account credentials or App Store Connect access.

Limitations

• Supports only the user-selected issue “IAP was not included with the app-version review submission.”
• Does not classify rejection messages, inspect an account, verify a completed fix, submit an app, guarantee approval, or provide legal advice.
• Official policy and procedures must be checked again on the resubmission date.
• The public Store CTA may use generic wording; confirm the adjacent US$19 event price before starting a run.

Local test

The tests use Python's standard library and do not call Apify or the network:

python -m unittest discover -s tests -v

The regression tests verify the narrow input/output, safety, and billing-call contract. They are not evidence of App Store resolution or approval.

The deployed entry point requires the package pinned in requirements.txt and runs python -m src through Dockerfile.