Hi Shopify Support,
We received an App rejection where the reviewer recorded a video showing our Flow template extension was not found in the Flow template library, and stated they couldn’t test our app’s core functionality as a result. Our app has not been published yet.
According to your own documentation (Flow template reference: Flow template reference ), public apps must be listed on the Shopify App Store before a Flow template extension can be submitted for review. This means our template cannot be approved or live in the public library prior to our app being published — so we don’t understand how the reviewer was expected to find it there.
Could you please clarify the following:
- Given that templates can’t be submitted for review until the app is listed, how is the App Review team expected to test a Flow template belonging to an unpublished app? Are they expected to test the draft version in a dev store, or via the flow-connector-testing.myshopify.com account referenced in your docs?
- Does running
shopify app deployautomatically submit our Flow template extension for review, or is a separate submission step required? - Is there a status page (Partner Dashboard or Dev Dashboard) where we can check whether a template is in the review queue, approved, or rejected — separate from email notifications?
- If a template is rejected, is there any location besides the email notification where we can view the rejection details/feedback?
- We have separate development and production apps. Can you confirm: (a) a Flow template deployed from our dev app is scoped only to that app, and (b) our production app needs its own independently deployed template extension for App Review to test?
- Given the sequencing issue above, what is the correct/expected order of operations for a first-time submission — should we expect App Review to test against our dev store’s draft template, and only submit the template for official Flow approval after the app is listed?
We want to make sure we follow the correct workflow before resubmitting, and would appreciate confirmation from someone on the Flow team if possible, since this seems to be a gap between the documented process and what our reviewer expected.