Skip to content

Android AAB file doesn't build with the increased build number #3916

@henrroga

Description

@henrroga

Can we access your project?

  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

When I do a mobile deployment for Android and download the AAB file, I cannot do a release in Play Store because it tells me you already have released this build, although I increased the build number in FlutterFlow.

Expected Behavior

The release in Play Store should work correctly getting the new build number from FlutterFlow.

Steps to Reproduce

  1. Deploy to Internal track in Play Store
  2. Download the AAB file
  3. Upload it in Play Store
  4. Check the version code

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

ITFThcj6389Om+FC+KriL8BKqDssGUMdXOczitVEew4bCIj4OqQLO8z7M0xuTdyzaH9Yf1qgkl0dpKGOk/DxDsFdCzGuR7pC1odqYBPPbEK5brqbEZaNOGpCRZ9WGkyA17SRpCYkKtpvWCEHwUyMO+i9Fj6Cf9qOYwx5e6fDbOY=

Visual documentation

CleanShot 2024-09-27 at 16 01 06
GYd2U7mWkAATjUI

Environment

- FlutterFlow version: v5.0.0+ (released Sep 27, 2024)
- Platform: Web
- Browser name and version: Brave Version 1.69.168 Chromium: 128.0.6613.138 (Official Build) (arm64)
- Operating system and version affected: macOS Sonoma 14.1.1

Additional Information

I cannot release an update to Android, this seems really urgent!

Metadata

Metadata

Assignees

Labels

status: needs triageA potential issue that has not been confirmed as a bug.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions