Compatibility reports wanted: tell us how the setup script ran on your machine

[saty-a]

All three platforms are implemented now. The most useful five-minute contribution: run the script for your platform and say what happened.

Please open a compatibility report (or comment here) with:

• OS version and architecture (Windows: winver and $PSVersionTable.PSVersion)
• Whether the machine was clean, or already had Flutter / Android Studio / a JDK
• Whether you were on a corporate network, proxy or VPN
• The final summary table, and the exit code
• Anything that needed a manual fix afterwards

Successful runs are as valuable as failures — they are what turns "should work" into "known to work". For failures, attach the log from <install root>/logs/ (skim it first; it contains your username, machine name and full paths).

Specifically wanted, because I could not test these

• Intel macOS — macos/setup.sh was verified on Apple Silicon only.
• A real x86_64 Linux machine — linux/setup.sh was verified in an emulated container, which is not the same as bare metal.
• Distros beyond Ubuntu and Fedora — Arch, openSUSE and Alpine package-name hints are reasoned from /etc/os-release, not verified.
• Windows behind TLS inspection (Zscaler/Netskope-style) — the hardest path to verify alone, and the one most likely still wrong.

Already verified: Windows 10/11, macOS 15 on Apple Silicon, Ubuntu 24.04 x86_64 (container).