Skip to main content
Submitting sends your app to a Fanvue reviewer from the App details page, and an approved app goes live on the App Store for creators to install. Only off-platform and on-platform apps submit. Before you click Submit for review, complete the checklist below, meet the listing requirements and test the app end to end against the live API with Test your app.

​
Before you submit

The submission bar on App details counts the steps left until every item is complete, and the checklist names each missing item: Highlights are optional, 1 to 5 of up to 40 characters each. When an app domain is stored, an app that has never been published also needs its manifest status to be Up to date or Out of sync; see First publish with a manifest.

​
Submit dialog

Submit for review opens the App Review Details dialog with two sections. Test credentials take a username, a password and notes of up to 500 characters. The account must be active, have full admin privileges and not require any payment. Create a dedicated test account for reviewers, and never enter your own login. Reviewers run the submitted app as a creator through a temporary preview that uses the same launch path a creator uses, so the account must work in your app end to end. What’s changed in this version (optional) takes change notes of up to 500 characters. Fanvue appends an Automatic change summary of the listing fields that differ from your live version, with lines such as “Updated tagline” or “Updated preview images”. The summary is stored in English whatever your interface language.

​
Statuses

The App details page shows one pill for the app. Version history shows the status of each submission.

​
What approval changes

Approval assigns your app a content category and a content rating, and a reviewer can’t approve without them; see App Store content categories. Approval also changes four things:
  • Pending pricing plans are activated, so creators can pay for them. See Pricing plans.
  • Your own draft install becomes an ordinary install and counts like any other.
  • The approved submission replaces the previously approved version.
  • Scope additions the submission requested are applied on the next manifest check.
Rejection changes none of these. Your draft install stays a draft install.

​
Resubmit

Editing a live app’s details, or a manifest check that changes access or surfaces, creates a new draft. The live version keeps serving until the new submission is approved. Click Resubmit for review to submit the draft; scope additions apply when that submission is approved. To edit a submission that is in review, click Withdraw submission and confirm Withdraw. You can resubmit later. Withdrawing the only submission of an app that has never been approved also ends your own draft install.

​
Withdraw a live listing

Fanvue’s team takes an approved app off the App Store for you; there’s no self-serve withdrawal. Withdraw from App Store on the publish page explains this and opens the builder community on Discord, where you ask the team to withdraw the listing. Withdrawing a listing is the only case that uses Discord.

​
Ship manifest changes to a live app

Redirect URIs and webhook destinations in your manifest apply on every check, with no review. A scope added after your app is published waits for review, and so do changes to access (app type, app URL, fan experience URL, post-install URL) and surfaces. To ship those:
  1. Deploy your manifest and click Check now on the Versions tab. The check stages the new values onto your draft. The status becomes Out of sync, and App details shows Live · manifest changed with each change listed under Changed fields.
  2. Click Resubmit for review.
  3. Your live app keeps its published configuration until the new version is approved.
Republish to apply on the Versions tab writes the manifest values onto your draft without submitting it. It appears only while the status is Out of sync. To drop the changes instead, change the file back to the published values, deploy and click Check now. A manifest that removes the fan experience surface is refused at check. Remove the surface in Embed settings instead, where you confirm the impact on paid experiences first; see Removing a fan experience.