-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
org.gradle.tooling.BuildException: invalid code lengths set #47
Comments
I am having same issue, does anyone find any solution? |
invalid code lengths set |
me too having same issue, any luck in finding solution for this, anyone? |
I am having same issue :/ help me please .. |
The only solution I came up with is by downgrading your project level gradle to 3.1.0. It seems to be working on it. The only reason why I think it is causing the problem is latest gradle plugin try to validate every file in your project and somehow it cant read the shape_predictor_68_face_landmarks.dat. |
build.gradle: buildscript {
} allprojects { task clean(type: Delete) {
} app gradle: android { // splits{ buildscript { } repositories { dependencies { //dlib gradle // required by POM android {
} configurations { dependencies { buildscript { } // call regular ndk-build(.cmd) script from app directory
} def NDKCommand() { apply plugin: 'com.jfrog.bintray' def siteUrl = 'https://github.com/tzutalin/dlib-android-app' // Homepage URL of the library install {
} task generateSourcesJar(type: Jar) { task generateJavadocs(type: Javadoc) { task generateJavadocsJar(type: Jar) { artifacts { Properties properties = new Properties()
} i've gone through so many references and tried by changing each and every line, i dont know what i did but magically it's started working. |
:) |
The solution is to explicitly declare your resource directory to the raw folder. Add the following snippet to your Module:app build.gradle file -
Tested and working. |
You're legend bro |
use the latest gradle |
I am getting this error when i am trying to build project.
The text was updated successfully, but these errors were encountered: