You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Migrate existing android/settings.gradle to the new file. #54566
This issue may is obsolete due to #135392 which covers this case. I doubt someone will implement another migration (than the manual docs), if we also don't plan to do this for more recent versions of settings.gradle.
I agree with @Gustl22, writing a migration tool to automatically migrate .gradle files in infeasible since these files basically contain executable code.
Such a tool would only work for the most basic apps that didn't edit their Android buildfiles.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
Gustl22 commentedon Oct 27, 2023
As migration by the tool is not planned we might need to upgrade it manually by prompting the user: https://github.com/Gustl22/flutter/tree/54566-settings-gradle-migration
It also would make sense to propose upgrading directly to #135392
Gustl22 commentedon Dec 21, 2023
This issue may is obsolete due to #135392 which covers this case. I doubt someone will implement another migration (than the manual docs), if we also don't plan to do this for more recent versions of
settings.gradle.jmagman commentedon Dec 21, 2023
@reidbaker can this be closed then?
bartekpacia commentedon Jan 9, 2024
I agree with @Gustl22, writing a migration tool to automatically migrate
.gradlefiles in infeasible since these files basically contain executable code.Such a tool would only work for the most basic apps that didn't edit their Android buildfiles.
github-actions commentedon Jan 24, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.