Develop Reference

Error: Could not find EOCD, after adding "splits" in Android

I am using the following splits code in my gradle to reduce APK size:
splits {
abi {
// Enable ABI split
enable true
// Clear list of ABIs
reset()
// Specify each architecture currently supported by the Video SDK
include "armeabi-v7a", "arm64-v8a", "x86", "x86_64"
// Specify that we do not want an additional universal SDK
universalApk false
}
}
When I run the app, the APK is generated fine, with reduced size and runs on Emulator.
But when I try to build APK file from Build > Build bundles/apks like
I get this error:
Execution failed for task ':app:packageAbcDebug'.
> A failure occurred while executing com.android.build.gradle.tasks.PackageAndroidArtifact$IncrementalSplitterRunnable
> Could not find EOCD in '....apk'
Possible solution:
- Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html
I only wanted to exclude "x86" architectures, to reduce the APK size and need to send the APK to my client. How do I fix this?

I was running into a similar issue during my build process, though I wasn't enabling split. Take it for what you will.
After digging through the source kit for PackageAndroidArtifact and other sources in Android, I discovered "EOCD" means "End Of Central Directory". That is, it's related to the end marker of the zip file that gets built when building your output. (The link to the comments in Android's source kit.)
In my own case, I discovered that even though I'm asking Android Studio to do a complete clean of my build directory, it's leaving the app-debug.apk build artifact file. (For reasons, I'm trying to package the debug version of our APK for internal testing.) And somehow that file got corrupted, which completely confuses the build process.
The resolution was to manually delete the apk file prior to running the build process. (In my case, it was found in my build's app/debug directory, next to the app/build directory.)
G'figure...

May be its late but here is the solution with reason for it to work.
Since we are using splits to create apks for each architecture build system needs a different name for each apk being generated.
Best solution is to provide a dynamic way of generating apk names.
Just go to app level build.gradle file
Add rules for release/debug build variants in buildTypes block inside android block like this
buildTypes {
release {
minifyEnabled true
shrinkResources true
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
applicationVariants.all { variant ->
variant.outputs.all { output ->
project.ext { appName = 'YourApkName' }
outputFileName = "${appName}-${output.getFilter(OutputFile.ABI)}-${variant.name}-${variant.versionName}.apk"
}
}
}
}
Explaination :
Here the apk name is appended by the ABI name that helps build system identify the apks for each architectures.

You can also use Android Size Analyze to identify sizes and reduces the apk size.
In order to understand which files are actually taking up more space in the application, use the Android Size Analyzer plugin inside Android Studio. For installing the plugin
Select File > Settings (or on Mac, Android Studio > Preferences.)
Select the Plugins section in the left panel.
Click the Marketplace tab.
Search for the “Android Size Analyzer” plugin.
Click the Install button for the analyzer plugin.
Restart the IDE after installing the plugin. Now, to analyze the application, go to Analyze > Analyze App Size from the menu bar.

After update gradle ver apk size twice bigger, why?

I had gradle
classpath 'com.android.tools.build:gradle:3.5.3'
distributionUrl=https\://services.gradle.org/distributions/gradle-5.4.1-all.zip
and my apk 160Mb
then I update it to
classpath 'com.android.tools.build:gradle:3.6.3'
distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.4-all.zip
and my apk size is 270Mb
How is it possible? But acctually if I build .aab it is still has 160Mb, so size increasing if I build .apk

This is caused by a change in the Gradle plugin which used to zip deflate the native libraries, but now just stores them. According to Google this ends up being a benefit for end users:
Smaller app install size because the platform can access the native
libraries directly from the installed APK, without creating a copy of
the libraries.
Smaller download size because Play Store compression is
typically better when you include uncompressed native libraries in
your APK or Android App Bundle.
According to that same link, you can revert this change by setting extractNativeLibs to true

add this tag on you AndroidManifest.xml file
android:extractNativeLibs="true"
example:
<application
android:extractNativeLibs="true"
... >
</application>

i had the same problem the only thing that help me little is to add abiFilter in build.gradle inside defaultConfig
ndk{
abiFilters "mips","mips64","armeabi","armeabi-v7a","arm64-v8a"
}

I had the same problem, but the provided solution was not working. For those having multidex enabled on your APK your must add the following instead:
android {
packagingOptions {
dex {
useLegacyPackaging true
}
}
}
on your module build.gradle
Source : https://developer.android.com/studio/releases/gradle-plugin#dex_files_uncompressed_in_apks_when_minsdk_28_or_higher

Android Studio Some file crunching failed, see logs for details

I have a problem with 9 patch images.
There are around 30 9 patch images in my res folder. On earlier versions of Android Studio, errors told me exactly which one of the images was bad, but on newer versions I just get error
Error:Execution failed for task
':app:mergePhotoKeyboardThemeChangerDebugResources'.
Error: java.lang.RuntimeException: Some file crunching failed, see logs for details
Is there an option for that in Android Studio settings? It is a lot of work to check images one by one and see which one is bad.

Some times the error will come with jpg images, try to convert the jpg images to png images.
convert online from online png converter.

Suggestion#1:
Relocate your project and the build will succeed.
Resource Link: https://stackoverflow.com/a/25209204
Suggestion#2:
Sometimes .png images are corrupted. you need to replace in drawable
Resource Link: https://stackoverflow.com/a/41380118
Suggestion#3:
change build directory
For example:
allprojects {
buildDir = "C:/tmp/${rootProject.name}/${project.name}"
repositories {
jcenter()
}
}
Rebuild and happy coding.
Resource Link: https://stackoverflow.com/a/41877283
Last Suggestion
Add
aaptOptions {
cruncherEnabled = false
}
in your gradle(app) file in android{ } scope
it will work fine

No difference in size of my apk with cruncherEnabled option disbled

I'm trying to reduce the size of my apk.
So first I've compressed my pngs with zopfli then added
aaptOptions {
cruncherEnabled=false
}
in my build.gradle (app) and built.
But the result is same with and without that option (gradle version 2.2.3)
Can anyone help?

how to speed up android studio build time in my project

I have 5 modules in my project, it takes me 2 mins to build everytime, is there any way to speed up android studio build time?

You can try to add this in your build.gradle file inside the android closure
dexOptions {
incremental true
javaMaxHeapSize "4g"
}
It will allocate large heap size for your dex process which usually takes more time in build.
You can change your your heap size according to RAM you have in your system like "2048M" for 2GB allocation.

Another idea might be using a faster repository. If your build is using mavenCentral() try to replace it with jcenter().

For me, adding the following two properties to the "gradle.properties" file in the project root improved performance considerably.
org.gradle.parallel=true
org.gradle.daemon=true
"org.gradle.parallel=true" does parallel processing of the modules. You may receive a message that the feature is experimental but it has worked for me without any problems.
"org.gradle.daemon=true" will keep a dedicated Gradle JVM running so that it is not re-started each time you do a build. This first build takes as long but subsequent builds are much quicker.
Hope this helps.

Yup you can speed up android studio build time.
1. You need to clean your project before building your project.
2. Close all other projects on which you are not working before build.
3. Allow auto build option.

According to this document https://developer.android.com/studio/build/multidex.html#dev-build
If you are using MultiDexApplication you can set minSdkVersion 21 for your develop productFlavors to mitigate the longer build times for multidex output.
productFlavors {
dev {
// Enable pre-dexing to produce an APK that can be tested on
// Android 5.0+ without the time-consuming DEX build processes.
minSdkVersion 21
}
prod {
// The actual minSdkVersion for the production version.
minSdkVersion 14
}
}