Introduction #
The Publishing Service streamlines the process of getting your mobile app live on the Apple App Store and Google Play Store. A dedicated Publishing Team member reviews your app and store listing to ensure compliance with strict app store guidelines, manages all communications with Apple and Google, and handles the submission on your behalf.
This guide walks you through preparing your iOS and Android apps, submitting a publish request, responding to recommended changes, and understanding how the Publishing Team supports you until your app is approved.
Before You Begin #
- Finalize all app customizations.
- Complete the Apple App Store Publishing Checklist or Google Play Store Publishing Checklist depending on the platform.
- Generate the required app screenshots for your white-label app.
- Avoid making changes to app store records during the publishing process to prevent delays.
Publishing Your iOS App #
- Complete the Apple App Store Publishing Checklist
Ensure every step in the checklist is complete before proceeding. - Access the Publishing Service
- In WordPress, go to Learndash App > Publishing Service > Apple App Store.
- In WordPress, go to Learndash App > Publishing Service > Apple App Store.
- Submit Your Publish Request
- Complete the Publishing Checklist questionnaire and confirm all required steps.
- Select the Release App build you wish to publish and click Confirm Build.
- Review and confirm the App Store Version.
- Choose whether the Publishing Team will respond to Apple on your behalf or if you will respond directly.
- Click Submit for Review.
- Complete the Publishing Checklist questionnaire and confirm all required steps.
Publishing Your Android App #
- Complete the Google Play Store Publishing Checklist
Ensure every step in the checklist is complete before proceeding. - Access the Publishing Service
- In WordPress, go to Learndash App > Publishing Service > Google Play Store.
- In WordPress, go to Learndash App > Publishing Service > Google Play Store.
- Submit Your Publish Request
- Complete the Publishing Checklist questionnaire and confirm all required steps.
- Select the Release App build you wish to publish and click Confirm Build.
- Enter your Google Developer Account ID from Google Play Console > Settings > Developer account > Account details.
- Confirm your Release Name and Release Notes.
- Choose whether the Publishing Team will respond to Google on your behalf or if you will respond directly.
- Click Submit for Review.
- Complete the Publishing Checklist questionnaire and confirm all required steps.
Responding to Recommended Changes #
If the Publishing Team identifies changes needed for app store approval:
- In WordPress, go to Learndash App > Publish > Apple App Store or Learndash App > Publish > Google Play Store.
- Under Have you made the recommended changes?, select:
- Yes – The team will review your updates before resubmitting.
- No – The app will be submitted as-is, increasing the risk of rejection.
- Yes – The team will review your updates before resubmitting.
- Under Do you want to change the build version?, select:
- Yes – Choose the new build to use.
- No – Continue with the same build.
- Yes – Choose the new build to use.
- Click Submit Response.
Responding to Apple and Google #
If Apple or Google rejects your app:
- You’ll receive an email outlining the reason(s) for rejection.
- If you opted for the Publishing Team to manage communications, they will respond and guide you through the required changes until approval.
- If you manage communications yourself, respond directly in the respective console and make the necessary updates before resubmitting.
Troubleshooting and FAQs #
Q: Why is my publish request delayed?
A: This is usually due to incomplete information, pending checklist items, or extended Apple/Google review times.
Q: Can I change app details while the Publishing Team is reviewing my request?
A: No. Any changes during the review may cause delays or rejection.
Q: I selected the wrong build. What should I do?
A: Submit a new publish request with the correct build.
Q: Why was my app rejected?
A: Common reasons include guideline violations, missing privacy policies, incomplete metadata, or functional issues in the build.
Q: Do all changes require a new build?
A: Only functional or design changes require a new build. Metadata-only changes can be submitted without generating a new build.