Andrew Kolos

I am reopening and unlocking this issue, because it is likely to reappear in an upcoming patch. This is because https://github.com/flutter/flutter/pull/128621 landed, which will effectively revert the fix for this....

> Are there two issues here? This one looks like an issue with arm64 linux hosts while #111764 is tracking codesigning and notarization of binaries for macOS. This is likely...

> I am not sure what aspect @andrewkolos was tracking. If its the arm64 hosts issue, then thats fine. Either way, @jonahwilliams is going to ping @andrewkolos to get more...

Unassigning since I am not confident I will find time to work on this within the next 2-4 weeks.

I'll be closing the issue since this appears to be resolved[^1]. Many of the recent here comments seem to have gone off topic and are instead discussing https://github.com/flutter/flutter/issues/139289 (and its...

@ditman friendly ping

It looks like this isn't making progress, either to being blocked or not being of high enough priority. Sorry about this. I'll be closing this PR just to get it...

FYI I updated this branch to include the fix from https://github.com/flutter/flutter/commit/6967ae551eaff91e2d0b483f31564993803282d6. See https://github.com/flutter/flutter/pull/140284#discussion_r1607178219 for my latest thoughts.

Thanks for contributing this. Since this PR has gone several weeks without a response to feedback, I'll be closing this PR just to get it off of our PR review...

Thanks for all of your effort in this contribution. When taking into account the 1) current top priorities of the Flutter CLI (quality/reliability), 2) the complexity/riskiness of this change, and...