You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
improve error message when gradlew assembledebug is used with -Pdart-defines that are not base64 encoded #95116
I propose a better error message when -Pdart-defines are not base64 encoded.
With Flutter 2.5 the following message is output: "Error parsing assemble command: your generated configuration may be out of date. Try re-running 'flutter build ios' or the appropriate build command."
This message didn't help. Only a search for the message in the flutter_tools source revealed the true cause of the problem:
A message containing a hint about the required base64 encoding would be more helpful for many developers using integration tests with CI. They will probably use -Pdart-defines to add some parameters for their tests.
Steps to Reproduce
in android folder of any project
run ./gradlew app:assembleDebug -Pdart-defines=MY_ENV=whatever
Task :app:compileFlutterBuildDebug FAILED
Error parsing assemble command: your generated configuration may be out of date. Try re-running 'flutter build ios' or the appropriate build command.
A gradlew task with correct base64 encoded dart-defines build without problem.
The issue is just the misleading error message.
./gradlew app:assembleDebug -Pdart-defines=TVlfRU5WPXdoYXRldmVy
...
BUILD SUCCESSFUL in 15s
Task :app:compileFlutterBuildDebug FAILED
Error parsing assemble command: your generated configuration may be out of date. Try re-running 'flutter build ios' or the appropriate build command.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
darshankawar commentedon Dec 13, 2021
christopherfujino commentedon Jan 28, 2022
@schilken is there a reason you are directly calling
gradlew app:assembleDebugrather than calling it via the flutter tool?schilken commentedon Jan 28, 2022
@christopherfujino We build the apks to deploy them into perfecto, our test service provider, as it is described here for the Firebase Test Lab:
https://github.com/flutter/flutter/tree/master/packages/integration_test#firebase-test-lab
christopherfujino commentedon Jan 28, 2022
Ahh, I see, that seems a reasonable use case :)
Improve error message when `dart-define` content are not `base64 enco…
Improve error message when `dart-define` content are not `base64 enco…
github-actions commentedon Apr 15, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.