Skip to content

"Initialize default-app-flavor (#169581)" fails flavors_test_macos #169598

Description

@matanlurey

... and flavors_test_ios, which caused it to be reverted:

As far as I can tell, it's the last step of the integration test which fails.

I can reproduce locally by doing the following:

  1. Build (debug) dev/integration_tests/flavors for macOS
  2. Edit flavors/macos/Flutter/ephemeral/Flutter-Generated.xcconfig:
- FLAVOR=paid
+ FLAVOR=free
  1. Run the following:
flutter-dev drive lib/main.dart --flavor=paid -d macos --use-application-binary="build/macos/Debug-paid/Debug Paid.app

Before #169298, this would pass (the flavor would be paid), but after the flavor is free (incorrect).

Activity

  1. self-assigned this
    on May 28, 2025
  2. added
    a: tests"flutter test", flutter_test, or one of our tests
    P1High-priority issues at the top of the work list
    team-toolOwned by Flutter Tool team
    on May 28, 2025
  3. added theissue type on May 28, 2025
  4. matanlurey commented on May 28, 2025

    @matanlurey
    ContributorAuthor

    What it looks like happened is I broke the following:

    if (!await runXcodeBuild(
    platformDirectory: path.join(projectDir, 'macos'),
    destination: 'platform=macOS',
    testName: 'flavors_test_macos',
    configuration: configuration,
    scheme: 'paid',
    actions: <String>['clean', 'build'],
    extraOptions: <String>['BUILD_DIR=${path.join(projectDir, buildDir)}'],
    skipCodesign: true,
    )) {
    throw TaskResult.failure('Build failed');
    }

    This used to compile the Kernel snapshot with paid, but now it doesn't.

    To debug, I'm doing the following semi-miserable workflow:

    cd dev/integration_tests/flavors/macos
    rm ../../../../bin/cache/flutter_tools.stamp
    
    # Edit code in flutter_tools
    
    xcodebuild -workspace Runner.xcworkspace -scheme paid -configuration Debug-paid
  5. github-actions commented on Jun 11, 2025

    @github-actions

    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.

  6. locked as resolved and limited conversation to collaborators on Jun 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work lista: tests"flutter test", flutter_test, or one of our teststeam-toolOwned by Flutter Tool team

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions