Skip to content

Conversation

@MattHeaney23
Copy link

Motivation / Description / Changes introduced

  • A common area of confusion is how to submit a new iOS app with subscriptions
  • This leads to a lot of people submitting their subscriptions to Apple in the wrong way, which can result in their new app being rejected
  • This guide leads people from uploading their app via Xcode, to checking everything is set up correctly with their subscriptions, to attaching those subscriptions to their new app release

Additional comments

  • I am also working on a video to be attached to this document, but this will be added in a future PR
  • This guide focuses on subscriptions, and does not cover other areas of setting up an app in App Store Connect, but there is scope to add this in the future
  • This guide assumes subscriptions are already set up and tested in the app

Tests

  • Typo and Prettier pass in the pre-commit hook

Readded removed content from merge

Small fix

Fix to the accidental removal

Additional fix to the removal

Reapplied

Fix to the weird formatting
Copy link
Member

@codykerns codykerns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love the guide 👏 great work! just a couple of tweaks 😄

hidden: false
---

# Submitting an iOS Subscription App
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

docusaurus will add the top-level title (H1, #) automatically, so in the content, we should have the highest level be H2, ##

slug: "/test-and-launch/app-store-rejections",
}),
Link({
label: "iOS Test",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's use a more descriptive label here 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants