Kotlin stdlib version incompatibility causes build failure (APK/Store)

[Camelossauro]

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 attempting to build an APK or publish to the app stores, the build fails with a fatal Kotlin version incompatibility. The build environment expects Kotlin 2.1.0, but a dependency is pulling kotlin-stdlib 2.3.10, causing the task :app:compileReleaseKotlin to fail. It is impossible to generate any Android build.

Expected Behavior

The build should complete successfully and generate a valid Android APK / publish to the app stores without any Kotlin version conflicts.

Steps to Reproduce

1 - Open an existing FlutterFlow project (Basic plan)
2 - Navigate to the build menu
3 - Select "Download APK" or "Publish to Play Store"
4 - Wait for the build to complete (~5 minutes)
5 - Observe that the build fails with a Kotlin stdlib version incompatibility error

Reproducible from Blank

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

Bug Report Code (Required)

ITEezcjfsIlOpb1H+ZPyKOxWpwMwJ0QlUIInj+0bWRMhfYioPbAIZsnCTBRLYte4eWNbPmaWnXIFpfDpi/zDFsYpNTOef60++a5XQQ6VIXOgaKqOEZCKYH8mJ+9WfRDE18CKkRF4PvphS1oF3ziye/CrG3qCf9qOYwx5e6fDbOY=

Visual documentation

Environment

- FlutterFlow version: v6.6.13 (released March 20, 2026)
- Platform: Web
- Browser name and version: 146.0.7680.80
- Operating system and version affected: Windows 11 Version 25H2

Additional Information

This issue completely blocks the app publishing workflow. I am unable to generate any Android build (APK or Play Store release), which means the app cannot be tested on real devices or published to users.
The issue appears to be on FlutterFlow's side, as the build environment expects Kotlin 2.1.0 but a managed dependency is pulling kotlin-stdlib 2.3.10. Since I am on the Basic plan, I have no access to code export and therefore no workaround available — I am fully dependent on FlutterFlow to fix this.

[Alezanello]

Hello,

I apologize for the late response. Does this issue still persist, or was it fixed in the latest FlutterFlow updates?

If not please contact support via in-app chat or support@flutterflow.io in order for them to help you with this issue that seems proejct specific