[theprantadutta]

While the licenses load, _PackagesViewState shows the app header (widget.about: the app name, version, legalese and "Powered by Flutter") above a CircularProgressIndicator, in a Column that can't scroll. When the two are taller than the screen, as on a landscape phone with large text, the column overflows. Once the licenses have loaded the page is fine, because the loaded list is a ListView.

The fix wraps the loading Column in a SingleChildScrollView.

Tests

One regression test in about_test.dart shows the page on a landscape phone (844x390) with the text scaled to 200%, and checks that the loading state doesn't overflow and that the progress indicator is inside a scrollable. It fails on main with A RenderFlex overflowed by 8.0 pixels on the bottom. and passes with the fix. The rest of about_test.dart passes, including the tests that check the page's color and Material count while loading (63 tests, plus one web-only skip), and so does the about_list_tile.0 example test.

Fixes flutter/flutter#195685

This is a draft because I'm at the open pull request limit for this repository. I'll mark it ready for review when a slot frees up.

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

I used AI tooling while working on this, and reviewed and tested all of it myself.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²