SubscriptionStoreView()

Question

Created 1w

Replies 1

Boosts 0

Participants 2

Hello,

SubscriptionStoreView() supports view modifiers such as .subscriptionStoreControlStyle(.automatic), which adapts naturally to the conditions

This is awesome. However, when I built the paywall, something caught my eye. The .automatic selection does not display what the user gets for the price, which goes against the guidelines?

I remember getting a rejection for this specific reason a few months ago. Here it is

Guideline 3.1.2(c) | Business | Payments | Subscriptions

Issue Description

The app uses auto-renewable subscriptions, but it does not clearly describe what the user will receive for the price.

Since this is a native component with native view modifiers, I assume the text placement, colors, and other styling choices are determined by Apple by default, which also suggests that it should comply with the guidelines?

My question is, will Paywall 1 pass the app submission review? Paywall 2 seems to make it clear what the user gets for the price

Thank you

Answer 1 · 7h

Pokpong OP

7h

Using SubscriptionStoreView doesn't guarantee review approval by itself. Guideline 3.1.2(c) applies to what the screen tells people before they subscribe: what they get and what it costs. StoreKit's view shows localized subscription names, descriptions and prices, and you can add custom marketing content above the choices. If the default product text doesn't explain the actual benefit, spell it out on the paywall, for example which features unlock or what usage limit changes. Make the subscription period and renewal price easy to see too.

I can't say whether Paywall 1 or 2 will pass without seeing the full screens and the product metadata. Apple's docs: SubscriptionStoreView and Guideline 3.1.2(c).