While developing Dragon Geo, I was always suspicious on why my APK was much larger than it should be, given my already optimized PNG files. Also, it greatly adds to the compile time for building your Android application. However, when you have already optimized your PNG files with tools like TinyPNG and offer greater savings than PNGcrush, this step is completely unnecessary.

Normally, this is a good step to perform prior to building the APK. It uses a built-in PNGcrush to reduce PNG file sizes as part of the process. As part of the packing process, aapt also performs file optimization on certain media files, such as PNG files. WARNING: the ability to disable packaging will disappear in 1.0įor those that are unfamilar with aapt, it is the SDK compile tool responsible for packing your app into an APK package.If you are disabling enforcement of package name, then you should disable packaging of BuildConfig with: android.packageBuildConfig = false.This requires that all your libraries have a unique package name. BuildConfig is now packaged in libraries.BuildConfig.VERSION_NAME is always generated even if the value is not set in the current variant.fixed issue where changes to the manifests of libraries didn’t trigger a new manifest merge.libraryVariant API now gives access to the list of flavors.

Generated POM files now have the proper dependencies even if the pom object is manipulated in adle.

WARNING: The ability to disable enforcement will disappear in 1.0.

To disable this you can use android.enforceUniquePackageName = false.

The plugin now enforces that all library dependencies have a unique package name.

WARNING: We’ve seen reports of the new processor generating PNGs that make the app crash on GB

To revert to the old cruncher: = true.

Fix issue where crunched png are bigger than original file.

Should be much faster when processing many files.

It’s now possible to include a file when there’s a conflict during packaging:.

Packagingoptions android studio gradle