Closed
Description
Hi,
I am trying to integrate fresco (0.5.1) on existing project with pre-build .so libraries. I found original .so files are no longer available in nativeLibraryPath (e.g. /data/app-lib/{PACKAGE_NAME}-N)
I found similar thread related to this #264, yet unable to get it work with creating the missing directories.
Activity
tyronen commentedon Jun 10, 2015
What does your
build.gradle
file look like?oosmarco commentedon Jun 10, 2015
build.gradle
directory structure of library project VideoRecorder
build.gradle of VideoRecorder
buildscript { repositories { jcenter() } dependencies { classpath 'com.android.tools.build:gradle:0.12.2' } } allprojects { repositories { jcenter() } }
./app/build.gradle of VideoRecorder
oosmarco commentedon Jun 11, 2015
We found all .so files are present in the apk file after unzipping with apktool, yet some of them can't be copied to devices nativeLibraryPath for some reason. Any clue for that?
Yet we managed to get the .so libraries included correctly by making separated apks (ref. http://frescolib.org/docs/multiple-apks.html)
kassim commentedon Mar 24, 2016
a common issue with native libs on Android is that if one native lib is available for an abi then all your native libs need to be available for that abi, it won't fall back to a lower supporting abi, so x86_64 won't fall back to x86
I had to put in this
in the android section of my build.gradle file
to allow a single apk build to work - though the better solution is to produce abi splits
expilu commentedon Mar 15, 2017
I'll leave this comment here for the people that might run into my same problem.
I have an app that uses both Fresco and Unity 3D (through a UnityPlayerActivity).
The Unity activity was crashing with the error "unable to find main". I noticed this only happened in devices with arm64-v8a.
Adding what @kassim said to the build.gradle file fixed the problem.