Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Comments

Upgrade to Flutter 3.38#1989

Merged
hjiangsu merged 2 commits intodevelopfrom
chore/flutter-3.38
Dec 3, 2025
Merged

Upgrade to Flutter 3.38#1989
hjiangsu merged 2 commits intodevelopfrom
chore/flutter-3.38

Conversation

@hjiangsu
Copy link
Member

@hjiangsu hjiangsu commented Dec 3, 2025

Pull Request Description

This PR upgrades Thunder to work with Flutter 3.38. I've also updated the relevant GitHub workflows to use the new version!

Additionally:

  • I've enabled the usage of Swift Package Manager to fix an issue related to background_fetch. For background_fetch, I've also removed the setup steps from Android as that is no longer required.
  • While attempting to upgrade package dependencies, I ran into some issues where some packages were locked at older versions. This was primarily due to xayn_readability using older dependencies. Since I don't quite have the time to maintain that package, and that package is not being actively maintained, I've decided to remove the reader mode for Android in the meantime.

Issue Being Fixed

Issue Number: N/A

Screenshots / Recordings

Checklist

  • If a new package was added, did you ensure it uses an appropriate license and is actively maintained?
  • Did you use localized strings (and added appropriate descriptions) where applicable?
  • Did you add semanticLabels where applicable for accessibility?

@hjiangsu hjiangsu merged commit 84b76d8 into develop Dec 3, 2025
1 check passed
@hjiangsu hjiangsu deleted the chore/flutter-3.38 branch December 3, 2025 21:54
@micahmo
Copy link
Member

micahmo commented Dec 4, 2025

Hey, I recently discovered something called Flutter Version Management (FVM). It really helps with working on multiple Flutter projects. Instead of having a global flutter with a fixed version for all projects, you use fvm to prefix all commands, and then it ensures that the right version is used for each project. So for this latest upgrade that you did, I just had to run fvm use 3.38.3, and then fvm flutter run or any other command like fvm flutter pub get and everything works great.

If you're interested in supporting FVM, it just adds these changes to the repo:

  • A .fvmrc file which just specifies the Flutter version
  • Ignoring the FVM cache (.fvm/) in the .gitignore
  • And since we use VS Code, it can also modify .vscode/settings.json so VS Code knows how to invoke the right version of Flutter

And it doesn't prevent anyone from continuing to just use flutter commands directly. But the configuration is available for anyone who happens to use FVM.

Here's another Flutter app that uses it:
https://github.com/pizi-0/flutter-scrcpygui/blob/main/.fvmrc
https://github.com/pizi-0/flutter-scrcpygui?tab=readme-ov-file#build-steps

Just a thought!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants