:app:generateCrashlyticsSymbolFileRelease - Specified path for unstripped native libs is not a directory

[Kocjan]

Describe your environment

    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.3'
        classpath 'com.google.gms:google-services:4.3.3'
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.0.0-beta02'
        classpath 'com.google.firebase:firebase-appdistribution-gradle:1.3.1'
    }

Describe the problem

Steps to reproduce:

When I try to run:
./gradlew clean assembleRelease uploadCrashlyticsSymbolFileRelease

I get next error:

Execution failed for task ':app:generateCrashlyticsSymbolFileRelease'.
> java.io.IOException: Specified path for unstripped native libs is not a directory: /Users/martin/repos/example-app-android/app/obj

If I manually move all my NDK libs to ./app folder I get the same error with different path:

Execution failed for task ':app:generateCrashlyticsSymbolFileRelease'.
> java.io.IOException: Specified path for stripped native libs is not a directory: /Users/martin/repos/example-app-android/app/build/intermediates/transforms/stripDebugSymbol/release

In this second case the build command sometimes fails, sometimes not.

This issue started to appear after I moved from Fabric Crashlytics plugin to Firebase Crashlytics plugin.
In the Fabric case, I had the option to define: androidNdkOut and androidNdkLibsOut paths.
Is that missing in the new Firebase plugin?

Relevant Code:

Old code example:

    crashlytics {
        enableNdk true
        androidNdkOut "$buildDir/ndklibs/obj"
        androidNdkLibsOut "$buildDir/ndklibs/libs"
    }

New Code example:

            firebaseCrashlytics {
                nativeSymbolUploadEnabled true

            }

In the Firebase case, I didn't specify any paths.

To collect all ndk libs I use following code:

    configurations {
        ndkzip
    }

    task setupNdklibs(type: Sync) {
        dependsOn configurations.ndkzip
        from {
            configurations.ndkzip.collect { zipTree(it) }
        }
        into "$buildDir/ndklibs/"
    }
    build.finalizedBy setupNdklibs

and executing ./gradlew build

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[mrichards]

In the new Firebase Crashlytics plugin, the androidNdkOut and androidNdkLibsOut properties have been changed to strippedNativeLibsDir and unstrippedNativeLibsDir, and should be declared in firebaseCrashlytics within the variant block, where you declared nativeSymbolUploadEnabled true.

Those options aren't currently documented, though they will be shortly.

[Kocjan]

@mrichards thanks for the info, I will test it and let you know.

[Kocjan]

@mrichards I tested and I get the same issues, but now the problem is with the path:

> java.io.IOException: Specified path for unstripped native libs is not a directory: /Users/martin/repos/example-app-android/app/Users/martin/repos/example-app-android/app/build/ndklibs/libs

It looks like this task prepends <your-path-to-app>/app to strippedNativeLibsDir and unstrippedNativeLibsDir paths.
Code:

            firebaseCrashlytics {
                nativeSymbolUploadEnabled true
                strippedNativeLibsDir "$buildDir/ndklibs/obj"
                unstrippedNativeLibsDir "$buildDir/ndklibs/libs"
            }

I solved my problem using relative paths:

            firebaseCrashlytics {
                nativeSymbolUploadEnabled true
                // These paths are relative to the app/ folder
                strippedNativeLibsDir "build/ndklibs/obj"
                unstrippedNativeLibsDir "build/ndklibs/libs"
            }

But it looks like a issue with the app:generateCrashlyticsSymbolFileRelease task :)

[mrichards]

Glad you got it working! I'll take a look at the absolute path issue.

[gordinmitya]

Hello, thanks for your answer @mrichards
What should I do if I have multiple modules with native code in my project?
How do I specify paths?

nativeSymbolUploadEnabled true doesn't work

this is my output of find . -name "obj" in the root folder of project

./mace/build/intermediates/cmake/release/obj
./mace/build/intermediates/cmake/debug/obj
./mnn/build/intermediates/cmake/release/obj
./mnn/build/intermediates/cmake/debug/obj
./ncnn/build/intermediates/cmake/release/obj
./ncnn/build/intermediates/cmake/debug/obj

[ihar-abramovich]

Hello, thanks for your answer @mrichards
What should I do if I have a separate module with native code and include it in a project like aar?
Is it possible to work with new Crashlytics this way?

[darrentaft]

I'm trying to use this myself for the first time and seeing this same error. I don't do anything special with cmake, I don't override any default directories, and I didn't specify any androidNdkOut parameters with the Fabric version.
Having switched to Firebase Crashlytics, I can't get it to upload symbols due to error:

Execution failed for task ':app:generateCrashlyticsSymbolFileSportProdStoreRelease'.
> java.io.IOException: Specified path for stripped native libs is not a directory: /home/vsts/work/1/s/app/build/intermediates/stripped_native_libs/sportProdStoreRelease/out

Any clues on how I can debug this? Do I need to specify the xNativeLibsDir params? If so, with what values? FYI "sport" and "prod" are flavor dimensions, and "storeRelease" is the buildType.

Note: the app has a number of 3rd party libraries and a module that include includes libraries, but I don't have debug variants of them to specify unstripped libs.

[synman]

Thanks to mrichards on the new operatives. I had this issue today after doing some housekeeping (deleting old obj folders / etc) within my app module.

My app module does not have any (direct) native libraries within it -- I just have a couple jars I need packaged and keep them in app/libs.

firebaseCrashlytics {
      nativeSymbolUploadEnabled true
      strippedNativeLibsDir "libs"
       unstrippedNativeLibsDir "libs"
 }

[marius-bardan]

Since both properties are relative paths to 'app' dir, how should I reference other modules? For example, my native libs are in ':external' which sits on the same leve as ':app' dir.
setting something like the following doesn't work:
strippedNativeLibsDir "${rootProject.projectDir}/external/build/intermediates/stripped_native_libs/release/out/lib/"

[4ntoine]

Yup, i'm also interested. Let's say :app depends on another android library (aar) with shared libs. I believe during the build they are extracted and collected somewhere in build dir. However i did not find not stripped libs (that are coming from aar) after assembleRelease just to adjust the paths. Anyone?

[marius-bardan]

This is what I'm currently using. But cannot attest it's correct due to another bug (NPE thrown when trying to upload symbols).

firebaseCrashlytics {
    nativeSymbolUploadEnabled true
    unstrippedNativeLibsDir "build/intermediates/merged_native_libs/release/out/lib/"
    strippedNativeLibsDir "build/intermediates/stripped_native_libs/release/out/lib/"
}