@Jasguerrero OK，i add it.

But I am a little confused, I think this command may be is bug? or he must rely on the previous command

1、if run assemble with dart-define options is error by current flutter version

flutter assemble --dart-define=k1=v1 -o Output debug_ios_bundle_flutter_assets

Error parsing assemble command: your generated configuration may be out of date. Try re-running 'flutter build ios' or the appropriate build command.

i want use encodeDartDefines but he has dedicated test cases testUsingContext('flutter assemble throws ToolExit if dart-defines are not base64 encoded', ,this description and implementation are somewhat ambiguous

2、The source code file assemble.dart

  @override
  Future<FlutterCommandResult> runCommand() async {
    final List<Target> targets = createTargets();
    final List<Target> nonDeferredTargets = <Target>[];
    final List<Target> deferredTargets = <AndroidAotDeferredComponentsBundle>[];
    for (final Target target in targets) {
      if (deferredComponentsTargets.contains(target.name)) {
        deferredTargets.add(target);
      } else {
        nonDeferredTargets.add(target);
      }
    }
    Target? target;
    List<String> decodedDefines;
    try {
      decodedDefines = decodeDartDefines(environment.defines, kDartDefines);
    } on FormatException {
      throwToolExit(
        'Error parsing assemble command: your generated configuration may be out of date. '
        "Try re-running 'flutter build ios' or the appropriate build command."
      );
    }

The code decodedDefines = decodeDartDefines(environment.defines, kDartDefines); is decode but you can't find where to code

Does this depend on the previous command, because the previous command is encoded ???

So I always feel that the implementation of flutter assemble is not good enough, or it is implemented separately compared to other operations such as build apk ios bundle ipa,
For example reference variable FlutterOptions.kDartDefinesOption only 2 place references

• AssembleComand#_parseDefines [private method]
• FlutterCommend#getBuildInfo [all other build/run cmd]

I don't think you need this remove, the past implementation you had in which you iterate over result and make an dartDefineConfigJsonMap.containsKey is the way to go. I understand that you weren't able to reproduce the dart define but you can mock the BuildInfo and send the dart defines there to encode

OK,i changed it another way, I don't know if it works @Jasguerrero

I still do not understand why you need this new variable systemVars if you just compare what the user send on the config file and what you already have on dartDefineConfigJsonMap wouldn't be enough?

I misunderstood, I thought you let me judge completely if the variable is duplicated. Because the above variable is conditional, if the condition is not satisfied, there is no variable, and I just set the above variable, which will cause coverage