r/flutterhelp • u/[deleted] • Mar 26 '24
RESOLVED Why does flutter run differently in debug/release?
Who thought this was a good idea? I just spent hours getting the layout of my app working correctly locally. I pushed it to my server thinking it was finally working and... blank screen and tons of errors.
Why would they allow invalid code to work when run in debug mode? I can't understand that decision. And the errors in release mode are absurdly opaque and provide no useful information. How do you guys deal with this?
2
u/Alternative_Guava_32 Mar 26 '24
I totally sympathise with this. You should expect the same result from a debug build as a release build. Give me more information to debug the issue in debug mode but don't give me a different result. Large projects often have a significant amount of information going into the consol.
1
1
u/RichCorinthian Mar 26 '24
Or can you provide some of these opaque error messages?
1
Mar 26 '24
I don't have the error anymore and was in incognito when I googled it.
It was something about "minified" and <id>
1
2
u/SwampThrowawayPgy69 Mar 26 '24
What happens when you run the app in release mode on your dev machine?
Are you definitely not getting any errors printed to console when in dev mode? When running in dev mode with debugger no flutter exceptions thrown?
Iâve seen an app ârunningâ in dev mode but throwing plenty exceptions all over the place, that same app didnât ârunâ when compiled in release mode. But then it was never correct in the first place. If youâve just been working on layout Iâd check that first.
Release mode code is minified on web and mobile which is the correct thing to do for a production client app. If itâs just a server but not really a production environment you can disable the minification and you will preserve your class and variable names. To understand debug messages from minified code you need to ask the compiler to output the source-maps (web) or debug symbols (android / iOS) and store them. Sentry has been good for me for production error catching and inspecting.
2
u/Classic-Dependent517 Mar 26 '24
So you havent tested your app on release mode and real devices before publishing?
1
1
Mar 26 '24
Itâs a great idea, in fact, native solutions work the same way, why would you need all the development resources in your builds that are target to the stores/server? It sounds that you are introducing layout bugs that tend to render in debug but in release the system prevents them from showing, check your console in the screens where this is happening, it will tell you which component is not being rendered properly
1
u/rio_sk Mar 27 '24
Posts a useless rant on some subreddit. Absurdly opaque error, doesn't even know what the error really was. That explains a lot about the programming experience.
2
u/MuhammedOzdogan Mar 26 '24
Could you please elaborate what kind of invalid code runs on debug mode?