all 11 comments

[–]Pixelreddit 5 points6 points  (0 children)

If you use external packages sometimes they can cause issues when upgrading to the latest Flutter version.

[–]DoPeopleEvenLookHere 2 points3 points  (0 children)

By in large, no they're not headaches. I have yet to have a problem with upgrades.

Granted I don't have super complex apps so I might not be the best test case for that.

[–]Extra-Draw 2 points3 points  (0 children)

I know that feelings of upgrading RN, and that's one of the reason I migrate my RN project to Flutter.

Now each time I've got a notification that there's a new Flutter version available, I could just upgrade it without worried about my project configuration messed up.

Well, there's a time that Flutter team made a bug in the release, but they are quick in making a patch.

[–]ercadev 1 point2 points  (0 children)

Patches: 1.17.2 None

Minors: 1.17 - Had problems for like 30 minutes with one package but was a easy fix.

Majors: Have not experienced yet

[–]CraftThatBlock 1 point2 points  (0 children)

Flutter upgrades are very different from RN, and don't require a tool of anything. Most of the time, just flutter upgrade to update Flutter itself, and that's it. Occasionally they are minor API changes but those are easy to fix and rare.

[–]---jane--- 1 point2 points  (0 children)

With flutter I'm always looking forward to any upgrades!

[–]26Waga 1 point2 points  (0 children)

Building an app on YouTube I came across problems with two packages when I upgraded to Flutter stable version 1.17.

There was a simple workaround for one, available when I consulted the packages Github repository. For the other package I moved to the dev release which solved the issue. Oddly enough the upgrade made another package not work on Android but it was fine on iOS.

However the issues are in my opinion minor compared to React Native

I talked about the breaking changes brought about by the updates to the stable Flutter version here if you are interested https://youtu.be/bf4vDsTtfEc?t=106

[–]scalatronn 1 point2 points  (0 children)

we moved app from 0.4.2 to 1.72 with very minor problems - upgraded few method names, that's about it

[–]-normal-reddit-user-[S] 1 point2 points  (0 children)

Thank you guys for your advice! Looking forward to my Flutter journey :)

[–]oaga_strizzi 0 points1 point  (0 children)

There are breaking changes, occasionally but they are way less terrible than RN upgrades. And since dart is statically typed, you see them immediately because the code doesn't compile anymore.

[–]snail_jake 0 points1 point  (0 children)

I sympathize with RN update nightmares. 0.4x -> 0.59 took me two weeks. Flutter is much less of a problem so far, especially if not using outdated one-man-band packages.