Skip to main content

​
Android Publishing

Bfloat uses Expo EAS (Expo Application Services) to build your Android apps and prepare them for Google Play submission. This guide walks you through the complete publishing process.

​
Prerequisites

Before publishing to Android, ensure you have:
  • A Bfloat AI account
  • An Expo Integration configured
  • A Google Play Developer account ($25 one-time fee)

​
Step 1: Configure Your App

​
Package Name

Set your Android Package Name in project settings:
  1. Click Settings in your project
  2. Enter your Android Package Name (e.g., com.yourcompany.appname)
  3. Set your Project URL Slug
  4. Click Save Changes
Project Settings
Your package name must be unique on Google Play and cannot be changed after your app is published.

​
App Icons

Upload your Android app icon:
  1. Open Settings > App Icons
  2. Upload a 512x512 PNG image (or larger)
  3. Bfloat generates adaptive icons automatically

​
Step 2: Set Up Google Play Console

​
Create Your App

  1. Log in to Google Play Console
  2. Click Create app
  3. Fill in:
    • App name: Your app’s display name
    • Default language: Primary language
    • App or game: Select app type
    • Free or paid: Pricing model
  4. Accept the declarations
  5. Click Create app

​
Configure Store Listing

Before submitting, you’ll need:
  • App description (short and full)
  • Screenshots (phone and tablet)
  • Feature graphic (1024x500)
  • App icon (512x512)
  • Privacy policy URL
  • App category

​
Step 3: Build Your App

  1. Go to your project page in Bfloat AI
  2. Click the Publish button
  3. Select Publish to Android
Bfloat will use EAS Build to create your Android app:
Build PhaseDescription
QueuingBuild added to EAS queue
BuildingCompiling native Android code
SigningApplying upload key
CompleteAAB file ready for upload
Build times typically range from 10-20 minutes.

​
Step 4: Upload to Google Play

After the build completes:
  1. Download the AAB (Android App Bundle) file from the build
  2. Go to Google Play Console
  3. Navigate to Release > Production
  4. Click Create new release
  5. Upload your AAB file
  6. Add release notes
  7. Click Review release
  8. Click Start rollout to Production

​
Build Types

TypeFormatUse Case
AABAndroid App BundleGoogle Play (recommended)
APKAndroid PackageDirect installation, testing
Google Play requires AAB format for new apps. APKs are useful for testing or alternative distribution.

​
Google Play Review

Google reviews all new app submissions:
Review PhaseTypical Duration
ProcessingMinutes to hours
In Review1-7 days (new apps)
Approved/Rejected-
Subsequent updates typically review faster than initial submissions.

​
Common Rejection Reasons

  • Missing privacy policy
  • Incomplete store listing
  • Policy violations
  • Broken functionality

​
Viewing Build Status

Check your build status:
  1. Click Publish button
  2. Click View All to see all builds
  3. Check the Expo dashboard for detailed logs
Publish Status

​
Troubleshooting

​
Build Failed

  • Verify your Expo token has correct permissions
  • Check that your package name is valid
  • Review build logs in the Expo dashboard

​
Upload Rejected

  • Ensure your AAB is signed correctly
  • Verify package name matches Play Console
  • Check that version code is incremented

​
App Rejected by Google

  • Review the rejection reason in Play Console
  • Fix the identified issues
  • Submit a new build

​
Testing Before Release

​
Internal Testing

  1. In Play Console, go to Testing > Internal testing
  2. Create a release with your AAB
  3. Add tester email addresses
  4. Testers can install via Play Store

​
Preview Build

Use Expo’s preview builds for quick testing:
  1. Build with preview profile
  2. Install APK directly on device
  3. Test before submitting to Play Store

​
Resources