-
Notifications
You must be signed in to change notification settings - Fork 30.2k
flutter run fails on Android on Windows when installed in a path with non-ascii symbol #149194
Copy link
Copy link
Open
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: crashStack traces logged to the consoleStack traces logged to the consolefound in release: 3.22Found to occur in 3.22Found to occur in 3.22found in release: 3.23Found to occur in 3.23Found to occur in 3.23has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onplatform-androidAndroid applications specificallyAndroid applications specificallyplatform-windowsBuilding on or for Windows specificallyBuilding on or for Windows specificallyteam-toolOwned by Flutter Tool teamOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.Issues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool teamTriaged by Flutter Tool team
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: crashStack traces logged to the consoleStack traces logged to the consolefound in release: 3.22Found to occur in 3.22Found to occur in 3.22found in release: 3.23Found to occur in 3.23Found to occur in 3.23has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onplatform-androidAndroid applications specificallyAndroid applications specificallyplatform-windowsBuilding on or for Windows specificallyBuilding on or for Windows specificallyteam-toolOwned by Flutter Tool teamOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.Issues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool teamTriaged by Flutter Tool team
I suspect this is an underlying gradle issue rather than Flutter, but I failed to find a meta bug for this issue for
flutter_toolsso filing one.The root cause is that spaces an (in this case) non-ascii chars are almost always broken in tools (especially on windows) if they aren't covered in e2e testing, not due to the fault of the devs, rather that the fundamental building blocks of path handling are just broken on all systems, and so it's really hard to get all path handling correct.
In this case, non-ascii characters seem broken for at least android/gradle on windows, but possibly also other flutter commands.
To repro:
I tested locally by taking a stock flutter (not shorebird) copying it (to flutter2) and then renaming flutter2 to test_flutter木 (via explorer) and I also get failures from gradle when trying to run flutter out of test_flutter木
Even powershell seems confused by the 木.
This is the log from running a test within powershell within visual studio code:
shorebirdtech/shorebird#2140 is where this came in for Shorebird. https://github.com/shorebirdtech/shorebird/pull/2159/files is where we added a non-ascii char to our e2e tests for Shorebird, which passed everywhere but windows.