Skip to content

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

@andrewkolos

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.

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