Skip to content

When building a Flutter app, the flutter tool still generates an AssetManifest.json file that is unused by the framework #143577

Closed

Description

@andrewkolos

Before #122505 landed, the tool would generate a file named AssetManifest.json which was bundled into the flutter app being built. This file contained information about assets. After #122505, a new file gets generated, AssetManifest.bin, which succeeded AssetManifest.json. However, the tool still produces AssetManifest.json since some customers depend on it to determine what assets are available to an app at runtime. While this was never a publicly documented feature, it was recommended as a workaround to some users. In current times, the AssetManifest provides a supported way to do this, and we want users to use that instead.

We should announce a deprecation/removal of the AssetManifest.json concept, and remove all references to it in code.

Activity

  1. added
    P2Important issues not at the top of the work list
    c: tech-debtTechnical debt, code quality, testing, etc.
    team-toolOwned by Flutter Tool team
    triaged-toolTriaged by Flutter Tool team
    on Feb 16, 2024
  2. self-assigned this
    on Feb 16, 2024
  3. andrewkolos commented on Apr 25, 2024

    @andrewkolos
    ContributorAuthor

    We should announce a deprecation/removal of the AssetManifest.json concept...

    This has since been done. See the announcement for the timeline of when this issue should be fixed.

  4. added
    P3Issues that are less important to the Flutter project
    and removed
    P2Important issues not at the top of the work list
    on Jun 25, 2024
  5. andrewkolos commented on Jul 10, 2024

    @andrewkolos
    ContributorAuthor

    Unassigning since this is not actionable until at least February 15, 2025.

  6. removed their assignment
    on Jul 10, 2024
  7. self-assigned this
    on Jul 11, 2025
  8. added
    tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.
    on Jul 11, 2025
  9. github-actions commented on Aug 8, 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.

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

Metadata

Metadata

Assignees

Labels

P3Issues that are less important to the Flutter projectteam-toolOwned by Flutter Tool teamtool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions