When using GitHub Actions to automate a release build, after deploying to Play Store the app gets stuck after user login (if user is not logged in) or just get stuck (if the user was already logged).
Please check the following video:
In early August, I was able to generate a release build without any problem using "--no-shrink" parameter on the CLI, but for some reason, the same script isn't working.
I'm using the following configuration:
Gradle 7.5 (as in Flutterflow project)
Java JDK 18 (as per Gradle compatibility matrix)
Flutter 3.22.2 (as in Flutterflow environment)
From what I've investigated, the "--no-shrink" is deprecated in Flutter CLI and all release builds are now optimized, so the parameter is discarded.
https://github.com/flutter/website/issues/10032
I know this is not a Flutterflow specific issue, but the code should be buildable outside using the Flutter CLI, which is not the case.
I'm guessing this is some build environment configuration that is missing and is not in the project source code files.
This is the CLI command I'm using:
flutter build appbundle --build-name=${{env.BUILD_NAME}} --build-number=${{vars.BUILD_NUMBER_ANDROID}} --releaseI'm using this automation, so I can set multiple isolated environments, it was working fine until now....