Thanks for the quick reply. Super appreciated!
While the command:
flutter version
was not valid for my installation of flutter (perhaps it is --version ? maybe the markdown editor ate the double hyphens? Using backticks seems to help). I did discover I could do instead:
flutter downgrade
followed by:
flutter doctor
This brought me back to my previous version prior to my upgrade this morning. Now the flta projects built again, unmodified. What started me on the upgrade path, though, were warnings by flutter doctor to accept the android licenses, which then resulted in a crash:
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/android/prefs/AndroidLocationsProvider has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
As well, flutter doctor warning that Android Studio could not find the bundled Java version.
Doing the flutter upgrade fixed all that, but then broke the starter apps.
In exploring Flutter for our production work (enterprise apps), having a stable toolchain that doesn’t break our build process is important, especially if I’m going to convince my colleagues to try Flutter. Obviously not your team’s fault, and I’m sure you share the same concern for a different reason: the book source code goes stale quickly at the pace that Flutter evolves. Didn’t we go through something similar last year with Flutter 2…
That said, as you pointed out, with the interruptions of upgrades come improvements (we hope!).