Skip to content

[CP-beta]Disable multi-pack-index when calling flutter from Xcode#185100

Merged
auto-submit[bot] merged 2 commits into
flutter:flutter-3.44-candidate.0from
flutteractionsbot:cp-beta-6cc666c92098801536fc05d58abdad05314ec93c
Apr 16, 2026
Merged

[CP-beta]Disable multi-pack-index when calling flutter from Xcode#185100
auto-submit[bot] merged 2 commits into
flutter:flutter-3.44-candidate.0from
flutteractionsbot:cp-beta-6cc666c92098801536fc05d58abdad05314ec93c

Conversation

@flutteractionsbot
Copy link
Copy Markdown
Contributor

@flutteractionsbot flutteractionsbot commented Apr 15, 2026

This pull request is created by automatic cherry pick workflow
Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request.

Issue Link:

What is the link to the issue this cherry-pick is addressing?

#184376

Impact Description:

What is the impact (ex. visual jank on Samsung phones, app crash, cannot ship an iOS app)?
Does it impact development (ex. flutter doctor crashes when Android Studio is installed),
or the shipping of production apps (the app crashes on launch).
This information is for domain experts and release engineers to understand the consequences of saying yes or no to the cherry pick.

Xcode's version of git may conflict with user's version of git when determining the flutter content hash on macOS due to multi-pack-index incompatibility.

Changelog Description:

Explain this cherry pick:

  • In one line that is accessible to most Flutter developers.
  • That describes the state prior to the fix.
  • That includes which platforms are impacted.
    See best practices for examples.

< Replace with changelog description here >
[flutter/184376] When building an iOS or macOS app, the build may fail due to git multi-pack-index error.

Workaround:

Is there a workaround for this issue?

Disable multi-pack via env variable: #184376 (comment)

Risk:

What is the risk level of this cherry-pick?

  • Low
  • Medium
  • High

Test Coverage:

Are you confident that your fix is well-tested by automated tests?

  • Yes
  • No

Validation Steps:

What are the steps to validate that this fix works?

Run flutter build ios on computer with git version that contains this commit: git/git@105a22cf69

)

Flutter iOS and macOS apps call `flutter assemble` from within Xcode.
However, Xcode uses it's own version of git instead of the user's. This
causes an multi-pack-index incompatibility.

This PR disables the multi-pack-index config when running `git ls-tree`
to workaround this issue.

Fixes flutter#184376.

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [AI contribution guidelines] and understand my
responsibilities, or I am not using AI tools.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [x] I signed the [CLA].
- [x] I listed at least one issue that this PR fixes in the description
above.
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on [Discord].

If this change needs to override an active code freeze, provide a
comment explaining why. The code freeze workflow can be overridden by
code reviewers. See pinned issues for any active code freezes with
guidance.

**Note**: The Flutter team is currently trialing the use of [Gemini Code
Assist for
GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code).
Comments from the `gemini-code-assist` bot should not be taken as
authoritative feedback from the Flutter team. If you find its comments
useful you can update your code accordingly, but if you are unsure or
disagree with the feedback, please feel free to wait for a Flutter team
member's review for guidance on which automated comments should be
addressed.

<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview
[AI contribution guidelines]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines
[Tree Hygiene]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md
[test-exempt]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests
[Flutter Style Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md
[Features we expect every widget to implement]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes
[Discord]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md
[Data Driven Fixes]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
@flutteractionsbot flutteractionsbot added the cp: review Cherry-picks in the review queue label Apr 15, 2026
@flutteractionsbot
Copy link
Copy Markdown
Contributor Author

@vashworth please fill out the PR description above, afterwards the release team will review this request.

@flutter-dashboard
Copy link
Copy Markdown

This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter.

Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request implements a workaround for Xcode's git multi-pack-index incompatibility in bin/internal/content_aware_hash.sh by disabling the feature when Apple Git is detected. Reviewers suggested optimizing the detection logic by checking $OSTYPE first to avoid unnecessary process forks on non-macOS platforms and applying the git configuration consistently to all commands in the pipeline.

# Workaround for Xcode's git multi-pack-index incompatibility.
# https://github.com/flutter/flutter/issues/184376
GIT_OPTS=()
if [[ "$(git --version)" == *"Apple Git"* ]]; then
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Calling git --version on every invocation of this script adds a process fork to the startup path of every flutter command. Since this workaround is specific to Apple Git (macOS), consider checking the operating system first using the $OSTYPE variable to avoid this overhead on other platforms.

Suggested change
if [[ "$(git --version)" == *"Apple Git"* ]]; then
if [[ "$OSTYPE" == "darwin"* ]] && [[ "$(git --version)" == *"Apple Git"* ]]; then

if [[ "$(git --version)" == *"Apple Git"* ]]; then
GIT_OPTS=(-c core.multiPackIndex=false)
fi
git "${GIT_OPTS[@]}" -C "$FLUTTER_ROOT" ls-tree "$BASEREF" -- "${TRACKEDFILES[@]}" | git hash-object --stdin
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The workaround for multi-pack-index should also be applied to the second git command in the pipeline. If the environment or the specific Git version has issues with this feature, it could affect any Git invocation that initializes the repository context or reads the configuration, not just ls-tree. Applying it consistently ensures the fix is robust.

Suggested change
git "${GIT_OPTS[@]}" -C "$FLUTTER_ROOT" ls-tree "$BASEREF" -- "${TRACKEDFILES[@]}" | git hash-object --stdin
git "${GIT_OPTS[@]}" -C "$FLUTTER_ROOT" ls-tree "$BASEREF" -- "${TRACKEDFILES[@]}" | git "${GIT_OPTS[@]}" hash-object --stdin
References
  1. The style guide emphasizes doing things right when they are written. Applying the workaround consistently to all git commands in the pipeline ensures the fix is robust. (link)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is true and its something with ls-files that was failing.

@vashworth vashworth added the CICD Run CI/CD label Apr 15, 2026
@github-actions github-actions Bot removed the CICD Run CI/CD label Apr 15, 2026
@eyebrowsoffire eyebrowsoffire added CICD Run CI/CD autosubmit Merge PR when tree becomes green via auto submit App labels Apr 15, 2026
@auto-submit auto-submit Bot merged commit 92b3bf7 into flutter:flutter-3.44-candidate.0 Apr 16, 2026
174 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autosubmit Merge PR when tree becomes green via auto submit App CICD Run CI/CD cp: review Cherry-picks in the review queue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants