Android: Library not found: /native/linux/armv7l/

In my gradle script I have:
dependencies { compile fileTree(dir: 'libs', include: ['*.jar']) testCompile 'junit:junit:4.12' compile '' compile '' //compile 'com.couchbase.lite:couchbase-lite-android:1.2.1' //compile 'com.couchbase.lite:couchbase-lite-java-forestdb:1.2.1' compile 'com.couchbase.lite:couchbase-lite-android:+' compile 'com.couchbase.lite:couchbase-lite-java-forestdb:+' compile '' compile '' }
[After setting Manager to use ForestDB on NEW db,] When deploying apk to a hardware device on Android 4.2, I get:
System.err: Library not found: /native/linux/armv7l/ System.err: Error loading library: CouchbaseLiteJavaForestDB System.err: java.lang.NullPointerException System.err: at com.couchbase.lite.util.NativeLibUtils.loadLibrary( System.err: at<clinit>( System.err: at java.lang.Class.classForName(Native Method) System.err: at java.lang.Class.forName( System.err: at java.lang.Class.forName( System.err: at com.couchbase.lite.Database.createStoreInstance( System.err: at System.err: at com.couchbase.lite.Manager.openDatabase( System.err: at com.couchbase.lite.Manager.getDatabase( ...


@hideki Any input on this issue, please?


Hi @natgross,
Thank you for reporting another issue. It seems some Android devices return armv7l as an architecture. armv7l is variation of armv7. We need to fix native library loading code to address this.
I filed the ticket:

Ok. Thanks. Hopefully fixed for 1.3.

Hi @natgross,

it seems armv7l is armeabi device. Currently we could not compile ForestDB for armeabi and mips architectures.
ForestDB storage is only available for armeabi-v7a, x86, arm64-v8a, x86_64 and mips64 architectures.

To support old arm devices, please use SQLite storage.


@hideki, Thanks for the comeback. The thing is I am likely to use CBL for apps I hope to put out on the Play store. I won’t have additional app versions, with and without ForestDB. I will then need to branch my code based on the device architecture. The question is; Does CBL with ForestDB have the exact same API as SQLite storage? Is it just a matter of a better db engine, or does ForestDB introduce features not available with SQLite?


Feature set is the same, it’s just faster.

Thank you much.