Hi,
I have used the version 3.24.3 of Flutter without problems until now and I want to go to a new stable version. I know version 3.32 is out, but I’m affraid it can be a problem to my projects, facing issues I don’t know how to solve. So, which version do you recommend?
Any inability to upgrade your code to the latest libraries should be treated as technical debt, and given priority fix treatment.
That’s a bit of a smug take. Flutter sometimes introduces new bugs in new versions.
We are stuck on 3.24.3 for a while because of a bug in iOS that only recently got fixed but because of the change in the threading models in the latest release we first have to update our own native video player packages.
So in case you have any package that passes data to native Android threads you will have to be careful when upgrading to the latest versions.
4 Likes
Thanks for your answer @escamoteur. What I have used is the camera to take photos and GPS. So I think I’m gonna wait a little bit more.
If you only use the official plug-ins you should be save and you should see immediately if there is a problem, so I would just give it a try and try to build and run with latest Flutter
2 Likes
Great! I’m gonna try this using FVM. Thanks again!!!
I have an app that is stuck with 3.24.5. It’s the latest I can go without the app exploding in ANRs and crashes =(
3.27 is a no no! It does NOT work. 3.29 has some issues (in both cases I had to disable Impeller, but 3.27 would crash even with that disabled). Never had the courage to test 3.32 on production.
Eventually I’ll have to deal with it… and it WILL be a pain, so, if you can start something with the newer versions, go for it.
And try to use the least amount of packages available…
1 Like
I’d suggest ultimately give it a try. Things change across version and surely things may break but it might also fix some other things. Improve certain things.
Even allow newer version of packages that may then contain other fixes as well.
It’s specific to your app
But being afraid if it might break doesn’t solve anything, just give it a try on a branch 
1 Like
Thanks!! So do you consider testing the last version (3.32)?
I think it’s generally a good practice to checkout new stable version in the first few days after release just to see how many potential issues can you expect. For more “adventurous” it may be worth also checking the beta channel every now and then.
As you’ve noticed FVM (or other manager called puro) are great ways to quickly switch between Flutter versions. Make sure to commit your code before switching so that if something breaks you can safely return to your previous Flutter version and just discard all the changes that might have been applied. Sometimes Flutter can make modifications to your project or package versions on upgrade.
2 Likes
If Running an older flutter project that use dart version 3.3.0 then stable version is flutter 3.19.0
Otherwise 3.29.3 is stable for latest created projects.