· Selfmade - Dodo

Subscription Information - iOS

Integrations

Hey Flutterflow´s,

actually i am done developing my app. I am now at the finish line and get held hostage by apple dev preview team 😄

Apple Support after Review

Guideline 3.1.2 - Business - Payments - Subscriptions

Issue Description

The submission did not include all the required information for apps offering auto-renewable subscriptions. Apps offering auto-renewable subscriptions must include all of the following required information in the binary:

- Title of auto-renewing subscription, which may be the same as the in-app purchase product name
- Length of subscription
- Price of subscription, and price per unit if appropriate
- Functional links to the privacy policy and Terms of Use (EULA)

The app metadata must also include functional links to the privacy policy and Terms of Use (EULA).

Next Steps

Update the app's binary to include the following required information:

- Title of publication or service
- Length of subscription (time period and content or services provided during each subscription period)
- Price of subscription, and price per unit if appropriate
- A functional link to the Terms of Use (EULA)
- A functional link to the privacy policy

Update the app's metadata to include the following required information:

- A functional link to the Terms of Use (EULA). If you are using the standard Apple Terms of Use (EULA), include a link to the Terms of Use in the App Description. If you are using a custom EULA, add it in App Store Connect.
- A functional link to the privacy policy

I just have all these infos. I have a full subs. page, my component looks like this ->Even the Headlines are Matching perfectly with the apple auto renew subs. in app connect (i filled it manually to match.)

I have add the Subsription text beyond the last package fully viewable without scrolling (solution from flutterflow community / dev center).

The Price String loads perfectly from RC - (didnt show in Screenshot cause its from backend)

Terms of Use Link open a component with webview to -> https://www.iubenda.com/terms-and-conditions/14832847

so even this is completly in guidlines.

I compared my app view sub page / component with other apps -> and its all the same. the only

The only thing i hadnt update yet is the Metadata in AppConnect (description) - i didnt even know where and how to write it in the app description (dont get me wrong, in my meta desription is include that this app has free and premium components).

And where can i link my terms of use in app connect / metadata?!...or is there a problem that my policys and terms of use are viewable over the webview?!

Any ideas?! 🙂

Guideline 2.1 - Performance - App Completeness

Bug description: Subscription page was blank
Steps to reproduce bug:
Launch app.
Review device details:
- Device type: iPhone 13 mini
- OS version: iOS 17.5.1

I tested it on the same device and get perfectly my Sub. Pages - the component load works also fine so i dont get it. the only thing i can imagine is !web is as condition at my component - they also added a screenshot and i see a grey page, the same thing i got as !web wasn´t implemented and i checked flutter with webview - any advice for bug fixing - without reproduce its not quite simple.

--UPDATE--Solution--

Add in AppStore Description
Terms of Use: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/

Add below Paywal clickable as WebLink (Webview doesnt work)
Terms of Use: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/

After corresponding with apple support, all was fine, app is now published

What have you tried so far?
  • i change the ui several times

  • added the subsription text from flutterflow forum / dev text beyong the subscr. packages

  • changed the load time of RC - that RC Calls are done with app start and not after

  • answered the supports and waited for more interessting infos

  • change the view of my app completness check

  • checked on ipad and iphone to reproduce the error without luck

Did you check FlutterFlow's Documentation for this topic?
Yes
3
3 replies