- 
                Notifications
    You must be signed in to change notification settings 
- Fork 28
Description
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
Hello FlutterFlow Team,
I am unable to get a new AAB for my project. The build process seems to be stuck or failing, and always serves an old file.
Here is what we have diagnosed and tried:
- My build number is correctly incremented in my App Settings (e.g., to 8).
- The "Deploy to Play Store" feature fails. The logs show an error: "Google Play Android Developer API has not been used... or it is disabled."
- I have since located and successfully enabled this API in my Google Cloud project. I waited over 30 minutes for it to propagate.
- The deployment attempt still fails with the exact same error log.
- The "Download AAB" button also does not work. It either gives a "failed to get AAB url" error or downloads a very old build file with version code 1, which gets rejected by the Google Play Console.
It seems my project's build process is stuck in a failed state on your servers and is not recognizing that the API has been enabled.
Could you please check the build logs on your end for my project and help me get an up-to-date AAB?
Thank you.
Expected Behavior
When I click "Download AAB", I expect to download a new .aab file with the latest Build Number that I have set in my App Settings.
Steps to Reproduce
- Go to Settings > App Settings.
- Increment the "Build Number" to a new, unused number.
- Go to Settings > Mobile Deployment.
- Click the "Download AAB" button.
- Observe that the build fails or an old AAB file with an old version code is downloaded.
Reproducible from Blank
- The steps to reproduce above start from a blank project.
Bug Report Code (Required)
IT5TjPHhuJVOxLxH7arcbMEw+CQvH0A5a7sviu1uTRQaJuuuPLMTP8jCYXFIXNe+S3NcL1qZgj4d06nKk/PEA+UqYAedG9lq1c1+VAqWfGWWV5DROrmZOHB7L/hJJVyc0qSFviV+Wcl1c3Am11y6A+SidDTvNLLaCmwZBOWaVaT5nEmqQ0SLb3kNh1JWeC/v
Visual documentation
 
 
 
Environment
Not applicable, this seems to be a server-side build issue.Additional Information
This issue is a complete blocker preventing me from publishing my app. Thank you for your help!