Google Play publishing guide for Wrapply apps
Use this guide to understand how to publish your Wrapply-generated Android app using a signed AAB file, prepare Play Console requirements and manage future app updates.
What you need before publishing on Google Play
To publish a Wrapply-generated Android app on Google Play, you need a Google Play Console account, app metadata, a signed AAB file and the required policy information.
Required to create and manage your Android app listing.
The Android App Bundle generated by Wrapply or rebuilt from Flutter source code.
Name, short description, full description, category, screenshots and icon.
Privacy policy, app access, content rating, data safety and target audience.
Google Play publishing flow
Generate or rebuild the AAB
Use Wrapply to generate a signed AAB or build it from source code with flutter build appbundle --release.
Create the app in Play Console
Open Google Play Console, create a new app and set language, app name, app type and free/paid status.
Complete store listing
Add descriptions, screenshots, app icon, feature graphic and contact information.
Complete policy sections
Fill in Data Safety, App Content, Content Rating, target audience and privacy policy.
Upload the AAB
Create a production, internal, closed or open testing release and upload the signed AAB.
Submit for review
Check warnings, fix missing information and submit the app to Google review.
Updating an existing Android app
There are two different update types: updating the Flutter app code or updating the website content loaded by the app.
If you change AppBar, navigation, icons, package configuration, Firebase, permissions or native behavior, you must rebuild and upload a new AAB.
If you only change the content of the website URL loaded by the app, you usually update the website itself, not the app build.
Before uploading a new build, increase the version/build number in
pubspec.yaml.After rebuilding, upload the new AAB to Play Console as a new release.
version: 1.0.1+2
Build command:
flutter clean
flutter pub get
flutter build appbundle --release
Important Android publishing checks
Must be unique and should not change after publication.
Use the correct signing configuration for production releases.
Required if the app collects data, uses accounts, location, notifications or sensitive features.
Your website must load correctly and comply with Google Play policies.
FAQ
Do I need an AAB for Google Play?
Yes. AAB is the standard publishing format for Android apps on Google Play.
Do I need to rebuild when I change website content?
Usually no. If the app loads your website URL, content changes happen on your website. Rebuild only when the app code or native configuration changes.
Do I need to increase the version?
Yes. For a new Play Console upload, increase the version/build number in pubspec.yaml.