Skip to content
This repository was archived by the owner on Aug 8, 2025. It is now read-only.
This repository was archived by the owner on Aug 8, 2025. It is now read-only.

UnsatisfiedLinkError on Alps devices #11

@mingfai

Description

@mingfai

It's a rare case. My app deployed to over 1k devices and got only 2 exception reports. Both are Android 4.2.1.

The following are two different cases:
On a "alps ITOUCH HD2S":

java.lang.UnsatisfiedLinkError: Couldn't load leveldbjni from loader dalvik.system.PathClassLoader[DexPathList[dexElements=[zip file "/data/app/MY.PACKAGE-2.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]]: findLibrary returned null
    at java.lang.Runtime.loadLibrary(Runtime.java:359)
    at java.lang.System.loadLibrary(System.java:514)
    at com.litl.leveldb.DB.<init>(SourceFile:151)

On a "alps N9500"

java.lang.UnsatisfiedLinkError: Cannot load library: load_library(linker.cpp:761): not a valid ELF executable: /data/app-lib/MY.PACKAGE-1/libleveldbjni.so
    at java.lang.Runtime.loadLibrary(Runtime.java:365)
    at java.lang.System.loadLibrary(System.java:514)
    at com.litl.leveldb.DB.<init>(SourceFile:151)

-> MTK6589 -1209 MHz Quad-core

I don't think we should do anything to cater those unknown platforms. I fire the report just for record and please feel free to close it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions