Génération d'applications Android pour l'application MemberPress

Android Release Apps enable production-ready build preparation for Google Play submission, real-world testing, and accurate in-app purchase validation. Release Apps compile site configuration, branding, menus, and customizations into Android App Bundle files using cloud-based build servers. This document explains how to create Android Release App builds, upload them to Google Play testing tracks, invite testers, and manage build updates.

Release Apps are required for Google Play Store submission and verifying actual subscription pricing, durations, and purchase flows. Test Apps serve daily quality assurance and rapid development previews while Release Apps enable genuine in-app purchase transactions and official distribution testing. Proper Release App configuration ensures accurate pre-publication testing and smooth Google Play submission processes.

Comprendre les applications de mise en production et les applications de test

Les Release Apps et les Test Apps ont des objectifs différents dans le cycle de développement et de distribution.

Caractéristiques de l'application de test

Les Test Apps permettent un déploiement rapide pour les activités de développement et d'assurance qualité.

Assurance qualité quotidienne enables quick testing cycles without app store submission delays. Test Apps install via QR code without requiring Google Play distribution.

Stakeholder demonstrations showcase app features and functionality for approval processes. Direct installation simplifies sharing with non-technical reviewers.

Custom code previews validate GitHub-connected customizations before production deployment. Development teams test code changes without formal release procedures.

Achats simulés utiliser des prix fictifs sans traiter de transactions réelles. L'environnement de test permet de vérifier le flux d'achat sans implications financières.

Caractéristiques de l'application Release

Les Release Apps fournissent des versions de production pour la distribution et les tests officiels.

Google Play submission requires Release App AAB files for store publication. Only Release Apps meet Google's distribution requirements for public availability.

Real-world testing validates app functionality in production-equivalent environments. Testing tracks enable controlled Release Apps distribution before public launch.

Affichage des prix réels montre aux testeurs les coûts et les conditions réels de l'abonnement. La vérification des prix permet de s'assurer que les attentes des membres sont exactes avant la diffusion publique.

Transactions d'achat authentiques process real in-app purchase payments through Google Play billing. Transaction testing confirms proper payment processing and receipt validation.

AAB file format has met Google Play requirements since August 2021. Android App Bundle format enables optimized app delivery and reduced download sizes.

Creating Android Release App Build

Release App build generation creates production-ready AAB files for Google Play distribution.

1. Naviguez jusqu'à Tableau de bord > Application MP > Créer.
2. Cliquez sur le bouton Demander une compilation bouton.

3. Sélectionner Android comme plateforme parmi les options disponibles.
4. Sélectionner Lancer l'application comme type de construction.

5. Cliquez sur Prochaine étape pour passer à la configuration de la construction.
6. Cliquez sur Envoyer une demande de construction pour soumettre la demande de compilation.
7. Wait for build completion in the build queue.
8. Naviguez jusqu'à la page Historique de construction section.
9. Localisez la version achevée dans la liste de l'historique.
10. Cliquez sur Install on the Android device.  

11. Télécharger le fichier AAB à côté de la version finale.
12. Enregistrez le fichier AAB dans un emplacement sûr de l'appareil.

Note: Google requires AAB uploads for all new app submissions since August 2021. APK uploads remain possible only for apps previously published with the APK format.

Uploading AAB to Google Play Testing Track

Testing track upload enables controlled release testing before public distribution.

1. Connectez-vous à Google Play Console à l'adresse play.google.com/console.
2. Naviguez jusqu'à Toutes les applications et sélectionnez l'application dans la liste.

3. Naviguez jusqu'à Test et publication > Production to verify country and region settings.

4. Confirm target countries and regions are configured correctly.
5. Naviguez jusqu'à Release > Testing dans la barre latérale.
6. Sélectionnez l'option Closed testing track for in-app purchase quality assurance.
7. Cliquez sur Manage track next to the desired testing track name.

8. Cliquez sur Créer une nouvelle version pour commencer la création de la version.

9. Localiser le App bundles et APKs section.
10. Cliquez sur Télécharger to select the downloaded AAB file.
11. Naviguez jusqu'à la page Release details section after the upload completes.
12. Leave the auto-filled release name unchanged.
13. Paste release notes in the Notes de mise à jour domaine.
14. Cliquez sur Économiser to store the release configuration.
15. Cliquez sur le bouton Publication de la critique to proceed to the review screen.
16. Cliquez sur Start rollout to [track name] to publish to the testing track.
17. Wait for Google approval of the testing track release.

Remarque : Google approval timing varies from minutes to several days, depending on the review queue status.

Inviting Testers to Testing Track

The tester invitation enables specific users to access and install testing track releases.

1. Naviguez jusqu'à Release > Testing > Closed testing dans Google Play Console.
2. Cliquez sur le bouton Testeurs tabulation.

3. Localiser le Email lists section.

4. Select an existing email list or click Create email list for a new list.
5. Add tester email addresses matching their Google Play account emails.
6. Cliquez sur Enregistrer les modifications to store the tester list configuration.
7. Faites défiler jusqu'à How testers join your test section.

8. Copy the join link displayed in the section.
9. Share the join link with invited testers via secure communication.

Remarque : Tester email addresses must exactly match their Google Play account emails for successful access.

Configuring License Testing

License testing configuration restricts app access to authorized testers during testing periods.

1. Go to the Google Play Console dashboard.
2. Naviguez jusqu'à Settings > License testing in the Google Play Console sidebar.

3. Add the same tester email addresses from the testing track configuration.
4. Verify email addresses match Google Play account emails exactly.
5. Cliquez sur Enregistrer les modifications to finalize license testing configuration.

License testing ensures only authorized testers can install and access Release App builds during testing phases. Testers can now install Release Apps with full in-app purchase functionality enabled.

Updating Testing Track with New Builds

Testing track updates, deploy new Release App versions to existing testers.

1. Naviguez jusqu'à Tableau de bord > Application MP > Créer dans WordPress.
2. Cliquez sur Demander une compilation pour créer une nouvelle version.
3. Sélectionnez l'option Android platform and the Lancer l'application type de construction.
4. Complétez la demande de construction et attendez qu'elle soit terminée.
5. Téléchargez le nouveau fichier AAB à partir de Historique de construction.
6. Connectez-vous à Google Play Console à l'adresse play.google.com/console.
7. Naviguez jusqu'à Release > Testing > Closed testing.
8. Cliquez sur Manage track next to the testing track.
9. Cliquez sur Créer une nouvelle version to begin updating the release.
10. Upload the new AAB file in the App bundles et APKs section.
11. Complete release details with updated release notes.
12. Cliquez sur Start rollout to [track name] to publish update.
13. Testers receive update notifications through their Play Store testing link.

Testing track updates follow the same approval process as initial releases with similar review timelines.

Understanding AAB File Requirements

AAB file format requirements ensure compatibility with Google Play distribution systems.

Mandatory format applies to all new app submissions since August 2021. Google Play no longer accepts APK uploads for new applications.

Legacy APK support continues for apps previously published with the APK format. Existing apps can continue updating with APK files without the AAB conversion requirement.

Optimized delivery provides smaller download sizes through dynamic feature modules. AAB format enables Google Play to generate optimized APKs for different device configurations.

Version code increments must occur with each new AAB upload. Identical or lower version codes prevent successful upload and testing track deployment.

Best Practices for Release App Testing

Effective Release App testing validates functionality before public distribution.

Test purchase flows thoroughly with real payment methods before public launch. Verify that all subscription tiers and one-time purchases process correctly.

Verify pricing accuracy across all regions and currency configurations. Confirm displayed prices match intended costs for all markets.

Monitor crash reports during testing and track deployment to identify stability issues. Address crashes before expanding distribution to larger audiences.

Collect tester feedback systematically through designated channels. Structured feedback collection improves issue identification and resolution.

Update testing tracks regularly as development progresses and fixes deploy. Frequent updates keep testers engaged and provide continuous validation.

Document test results for reference during public release decisions. Comprehensive testing documentation supports launch confidence and risk assessment.