why is debug-apk size from 25.+ Mb is now 30.+ MB?

[Michael Tawiah Sowah]

Hi, before I updated my beta and dev channels, the counter template was 25.+ Mb after updating it's now 30.+MB.

I thought the recent cleanups of .flx and etc. was supposed to rather reduce the size or at least maintain.

 why has the size increase now? am currently on

on dev channel

[√] Flutter (Channel dev, v0.2.11, on Microsoft Windows [Version 10.0.17133.73], locale en-US)

    • Flutter version 0.2.11 at M:\flutter

    • Framework revision f408bb06f9 (5 days ago), 2018-04-10 14:27:53 -0700

    • Engine revision 6474647f52

    • Dart version 2.0.0-dev.46.0.flutter-ef926f98f5

[√] Android toolchain - develop for Android devices (Android SDK 27.0.3)

    • Android SDK at C:\Android\android-sdk

    • Android NDK location not configured (optional; useful for native profiling support)

    • Platform android-27, build-tools 27.0.3

    • ANDROID_HOME = C:\Android\android-sdk

    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java

    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)

    • All Android licenses accepted.

[√] Android Studio (version 3.1)

    • Android Studio at C:\Program Files\Android\Android Studio

    • Flutter plugin version 23.2.2

    • Dart plugin version 173.4700

    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)

[√] VS Code, 64-bit edition (version 1.22.2)

    • VS Code at C:\Program Files\Microsoft VS Code

    • Dart Code extension version 2.11.2

[√] Connected devices (1 available)

    • TECNO C9 • H535C90123456789 • android-arm64 • Android 6.0 (API 23)

• No issues found!

 

and beta 

[√] Flutter (Channel beta, v0.2.8, on Microsoft Windows [Version 10.0.17133.73], locale en-US)

    • Flutter version 0.2.8 at M:\flutter

    • Framework revision b397406561 (13 days ago), 2018-04-02 13:53:20 -0700

    • Engine revision c903c217a1

    • Dart version 2.0.0-dev.43.0.flutter-52afcba357

[√] Android toolchain - develop for Android devices (Android SDK 27.0.3)

    • Android SDK at C:\Android\android-sdk

    • Android NDK location not configured (optional; useful for native profiling support)

    • Platform android-27, build-tools 27.0.3

    • ANDROID_HOME = C:\Android\android-sdk

    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java

    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)

    • All Android licenses accepted.

[√] Android Studio (version 3.1)

    • Android Studio at C:\Program Files\Android\Android Studio

    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)

[√] VS Code, 64-bit edition (version 1.22.2)

    • VS Code at C:\Program Files\Microsoft VS Code

    • Dart Code extension version 2.11.2

[√] Connected devices (1 available)

    • TECNO C9 • H535C90123456789 • android-arm64 • Android 6.0 (API 23)

and both give the same results

[Eric Seidel]

Curious: are you looking at --debug or --release apk sizes?  We track --release APK sizes and so I would not expect to see an increase.

--debug sizes are not at all optimized and can fluctuate from build to build depending on how we change the debugging toolchain.

If you're seeing an increase in --release apk sizes, we'd love an issue: https://github.com/flutter/flutter/issues/new

--
You received this message because you are subscribed to the Google Groups "Flutter Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flutter-dev...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Tawiah Sowah]

@eseidel am talking about --debug

[Eric Seidel]

Ah yeah.  So --debug apks include all sorts of debug only tooling which makes them huge.  As noted, they can change size as we add/remove debugging features, we don't really make any effort to make --debug apks small at this time.

Is the --debug apk size causing an issue for you?  If so we'd love to learn more (again, probably via a Github issue is best).

Thanks.

[Michael Tawiah Sowah]

thanks @eseidel just wanted to be sure it's not something wrong with my flutter installation. thanks for the explanation...Flutter rocks