App getting crash

[bharathkandula99]

• Added a below line of code in my code base
  SQLiteDatabase db = SQLiteDatabase.openOrCreateDatabase(dbOutputFile, "password", null, null, null);

implementation 'net.zetetic:sqlcipher-android:4.5.2'
implementation 'androidx.sqlite:sqlite:2.1.0'

Here are the logs I am getting,

java.lang.UnsatisfiedLinkError: No implementation found for long net.zetetic.database.sqlcipher.SQLiteConnection.nativeOpen(java.lang.String, int, java.lang.String, boolean, boolean) (tried Java_net_zetetic_database_sqlcipher_SQLiteConnection_nativeOpen and Java_net_zetetic_database_sqlcipher_SQLiteConnection_nativeOpen__Ljava_lang_String_2ILjava_lang_String_2ZZ)
at net.zetetic.database.sqlcipher.SQLiteConnection.nativeOpen(Native Method)
at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:222)
at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:198)
at net.zetetic.database.sqlcipher.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:474)
at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:189)
at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:181)
at net.zetetic.database.sqlcipher.SQLiteDatabase.openInner(SQLiteDatabase.java:1029)
at net.zetetic.database.sqlcipher.SQLiteDatabase.open(SQLiteDatabase.java:1014)
at net.zetetic.database.sqlcipher.SQLiteDatabase.openDatabase(SQLiteDatabase.java:841)
at net.zetetic.database.sqlcipher.SQLiteDatabase.openDatabase(SQLiteDatabase.java:813)
at net.zetetic.database.sqlcipher.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:910)

[developernotes]

Hi @bharathkandula99

Are you using abiFilters or ProGuard in your build? If so, can you temporarily disable that and try your example again? Would you also verify the native library presence by unpacking your APK using Apktool?

[theBlbDan]

@developernotes
I finally made the move to sqlcipher-android from android-database-sqlcipher. I've been receiving crash reports from the wild on Nexus 5X devices. It looks similar to the one above. I do use ProGuard, but I don't have any feasible way to disable and test.

"PHONE_MODEL": "Nexus 5X",
    "BRAND": "google",
    "PRODUCT": "bullhead",
    "ANDROID_VERSION": "8.1.0",
    "BUILD":
    {
        "BOARD": "bullhead",
        "BOOTLOADER": "BHZ32c",
        "BRAND": "google",
        "CPU_ABI": "x86",
        "CPU_ABI2": "",
        "DEVICE": "bullhead",
        "DISPLAY": "OSM1.180201.031",
        "FINGERPRINT": "google\/bullhead\/bullhead:8.1.0\/OSM1.180201.031\/5455776:user\/release-keys",
        "HARDWARE": "batwing",
        "HOST": "xpce9.ams.corp.google.com",
        "ID": "OSM1.180201.031",
        "IS_CONTAINER": false,
        "IS_DEBUGGABLE": false,
        "IS_EMULATOR": true,
        "IS_ENG": false,
        "IS_TREBLE_ENABLED": true,
        "IS_USER": true,
        "IS_USERDEBUG": false,
        "MANUFACTURER": "LGE",
        "MODEL": "Nexus 5X",
        "PERMISSIONS_REVIEW_REQUIRED": false,
        "PRODUCT": "bullhead",
        "RADIO": "M8974A-2.0.50.2.22",
        "SUPPORTED_32_BIT_ABIS": ["x86"],
        "SUPPORTED_64_BIT_ABIS": [],
        "SUPPORTED_ABIS": ["x86"],
        "TAGS": "release-keys",
        "TIME": 1554922978000,
        "TYPE": "user",
        "UNKNOWN": "unknown",
        "USER": "android-build",
        "VERSION":
        {
            "ACTIVE_CODENAMES": [],
            "BASE_OS": "",
            "CODENAME": "REL",
            "INCREMENTAL": "5455776",
            "PREVIEW_SDK_INT": 0,
            "RELEASE": "8.1.0",
            "RESOURCES_SDK_INT": 27,
            "SDK": "27",
            "SDK_INT": 27,
            "SECURITY_PATCH": "2018-01-05"
        }
    }

java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/org.blueletterbible.blb-fHiuvBvgQ2gHHaR32Zn6NA==/base.apk"],nativeLibraryDirectories=[/data/app/org.blueletterbible.blb-fHiuvBvgQ2gHHaR32Zn6NA==/lib/x86, /system/lib, /vendor/lib]]] couldn't find "libsqlcipher.so"
	at java.lang.Runtime.loadLibrary0(Runtime.java:1011)
	at java.lang.System.loadLibrary(System.java:1657)
	at org.blueletterbible.blb.MainAppLauncher.onCreate(jarjar:3)
	at android.app.Activity.performCreate(Activity.java:7009)
	at android.app.Activity.performCreate(Activity.java:7000)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1214)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2731)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2856)
	at android.app.ActivityThread.-wrap11(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1589)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6494)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

[developernotes]

Hi @theBlbDan,

A couple of questions regarding your application configuration:

• Are you abiFilters within your build configuration?
• Do you deploy your application using Android App Bundles?

We had a long thread in the android-database-sqlcipher project awhile back here regarding a similar issue where the usage of both the ReLinker library and SplitInstallHelper were suggested as possible solutions. Are you using either of those currently?

[theBlbDan]

I saw issue 587 last night and read through it as well as this one.

I do use App Bundles and no on abiFilters. My minSDK is 24, so ReLinker won't be of any use. I don't believe that SplitInstallHelper is of any use when using App Bundles.

Of the 400+ crash reports I've received on this new build, it's only affecting three devices and is definitely on first installs. I'm only at 25% roll-out, so that is helping to keep it reduced.

Possibly related? Native library failed to load

[mandrachek]

I'm seeing this intermittently as well in our release builds (proguarded). Our debug builds don't seem to suffer from this problem.

[developernotes]

Hi @theBlbDan,

I'm sorry for the delay in response, I didn't receive a notification to your latest reply. This may be a stretch, but I did find this reference on StackOverflow ¹ which could be related to your specific release packaging. Would you mind taking a look and let us know if this change impacts the behavior you are seeing? Thanks!

Footnotes

1. https://stackoverflow.com/questions/62807988/android-app-bundle-only-native-library-failed-to-load ↩

[mandrachek]

@developernotes - FWIW, I'm dealing with straight APKs, no app bundles. I'm seeing this in my minified release builds (with proguard rules added ala #18 , but my debug builds work fine. Stack trace is a little bit different since we're using Room (and 4.5.5, so line numbers are a little bit different), but fails at the same nativeOpen call.

Fatal Exception: java.lang.UnsatisfiedLinkError: No implementation found for long net.zetetic.database.sqlcipher.SQLiteConnection.nativeOpen(java.lang.String, int, java.lang.String, boolean, boolean) (tried Java_net_zetetic_database_sqlcipher_SQLiteConnection_nativeOpen and Java_net_zetetic_database_sqlcipher_SQLiteConnection_nativeOpen__Ljava_lang_String_2ILjava_lang_String_2ZZ)
   at net.zetetic.database.sqlcipher.SQLiteConnection.nativeOpen(SQLiteConnection.java)
   at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:226)
   at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:202)
   at net.zetetic.database.sqlcipher.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:474)
   at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:189)
   at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:181)
   at net.zetetic.database.sqlcipher.SQLiteDatabase.openInner(SQLiteDatabase.java:1028)
   at net.zetetic.database.sqlcipher.SQLiteDatabase.open(SQLiteDatabase.java)
   at net.zetetic.database.sqlcipher.SQLiteDatabase.openDatabase(SQLiteDatabase.java:840)
   at net.zetetic.database.sqlcipher.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:359)
   at net.zetetic.database.sqlcipher.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:278)
   at net.zetetic.database.sqlcipher.SupportHelper.getWritableDatabase(SupportHelper.java:60)
   at androidx.room.RoomDatabase.inTransaction(RoomDatabase.kt:632)
   at androidx.room.RoomDatabase.assertNotSuspendingTransaction(RoomDatabase.kt)
   at androidx.room.RoomDatabase.query(RoomDatabase.kt:480)
   at androidx.room.util.DBUtil.query(DBUtil.java:75)
   at com.myapp.dao.AppStateDao_Impl$5.call(AppStateDao_Impl.java:124)
   at com.myapp.dao.AppStateDao_Impl$5.call(AppStateDao_Impl.java)
   at androidx.room.CoroutinesRoom$Companion$execute$4$job$1.invokeSuspend(CoroutinesRoom.kt:87)
   at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
   at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
   at java.lang.Thread.run(Thread.java:920)

We had to rollback to the 4.5.4 legacy library due to this issue.

[developernotes]

@mandrachek out of curiosity, do you have something like this within your ProGuard file:

-keepclasseswithmembernames class * {
    native <methods>;
}

If not, would you add it and let us know if the behavior is different with a release build?

[mandrachek]

Yes, that's already in our proguard-rules.pro

[developernotes]

@mandrachek if you disable ProGuard, but perform a release build does it still crash?

[mandrachek]

@developernotes - checking... yes, even with minification disabled, the release build crashes.

The only differences in configuration for us are pretty standard stuff - signing configurations, a couple manifest placeholders (release builds have canProfile set to true, debug builds have useCleartextTraffic set to true), and debug builds have isDebuggable set to true, and release builds (normally) have isMinifyEnabled (and proguard files set up)

[mandrachek]

@developernotes - I noticed that in the merged manifest, android:extractNativeLibs="false" is set on the <application/>.
I tried adding android:extractNativeLibs="true" in my manifest, and the packaging.jniLibs.useLegacyPackaging=true in my build.gradle.kts. The release build no longer crashes!

According to the tooltip, if extractNativeLibs is false, the libraries have to be stored and page-aligned. Is it possible the libsqlcipher.so in the aar is not page-aligned?

[mandrachek]

Well... I spoke too soon turns out that didn't solve the problem. It appeared to delay it. I was able to launch our app, login, download data, put it in a sqlcipher db, and then at some point, down the road, while using the app, blammo:

FATAL EXCEPTION: DefaultDispatcher-worker-3
    Process: com.myapp, PID: 27195
    java.lang.UnsatisfiedLinkError: No implementation found for long net.zetetic.database.sqlcipher.SQLiteConnection.nativeOpen(java.lang.String, int, java.lang.String, boolean, boolean) (tried Java_net_zetetic_database_sqlcipher_SQLiteConnection_nativeOpen and Java_net_zetetic_database_sqlcipher_SQLiteConnection_nativeOpen__Ljava_lang_String_2ILjava_lang_String_2ZZ) - is the library loaded, e.g. System.loadLibrary?
        at net.zetetic.database.sqlcipher.SQLiteConnection.nativeOpen(Native Method)
        at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:226)
        at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:202)
        at net.zetetic.database.sqlcipher.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:474)
        at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:189)
        at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:181)
        at net.zetetic.database.sqlcipher.SQLiteDatabase.openInner(SQLiteDatabase.java:1028)
        at net.zetetic.database.sqlcipher.SQLiteDatabase.open(SQLiteDatabase.java:1013)
        at net.zetetic.database.sqlcipher.SQLiteDatabase.openDatabase(SQLiteDatabase.java:840)
        at net.zetetic.database.sqlcipher.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:359)
        at net.zetetic.database.sqlcipher.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:278)
        at net.zetetic.database.sqlcipher.SupportHelper.getWritableDatabase(SupportHelper.java:60)
        at androidx.room.RoomDatabase.inTransaction(RoomDatabase.kt:632)
        at androidx.room.RoomDatabase.assertNotSuspendingTransaction(RoomDatabase.kt:451)
        at androidx.room.RoomDatabase.query(RoomDatabase.kt:480)
        at androidx.room.util.DBUtil.query(DBUtil.kt:75)
        at com.myapp.dao.AppStateDAO_Impl$5.call(AppStateDAO_Impl.java:124)
        at com.myapp.dao.AppStateDAO_Impl$5.call(AppStateDAO_Impl.java:120)
        at androidx.room.CoroutinesRoom$Companion$execute$4$job$1.invokeSuspend(CoroutinesRoom.kt:87)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
        at java.lang.Thread.run(Thread.java:1012)
        Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException:         [StandaloneCoroutine{Cancelling}@401291b, Dispatchers.IO]

[mandrachek]

@developernotes no luck.