Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    When installing an APK, it automatically extracts the libraries of the right arch type and has them available for System.loadLibrary. But, if you're trying to load a non-standard library, the installer won't know your app has 32bit native code.

  2. ,

    This is a sub-class of the LinkageError class and indicates that the JVM cannot find an appropriate native-language definition of a method declared as native. Compile a 64-bit version of your .dylib file.

Solutions on the web

via GitHub by Michael-Frank
, 1 year ago
/tmp/snappy-1.1.2-6ef04ce3-540b-4cba-ac30-16e113f48e19-libsnappyjava.so: /tmp/snappy-1.1.2-6ef04ce3-540b-4cba-ac30-16e113f48e19-libsnappyjava.so: cannot open shared object file: No such file or directory (Possible cause: endianness mismatch
java.lang.UnsatisfiedLinkError: 
 /tmp/snappy-1.1.2-6ef04ce3-540b-4cba-ac30-16e113f48e19-libsnappyjava.so: 
 /tmp/snappy-1.1.2-6ef04ce3-540b-4cba-ac30-16e113f48e19-libsnappyjava.so: 
 cannot open shared object file: No such file or directory (Possible 
 cause: endianness mismatch)	at java.lang.ClassLoader$NativeLibrary.load(Native Method)	at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1965)	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1890)	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1851)	at java.lang.Runtime.load0(Runtime.java:795)	at java.lang.System.load(System.java:1062)	at org.xerial.snappy.SnappyLoader.loadNativeLibrary(SnappyLoader.java:174)	at org.xerial.snappy.SnappyLoader.load(SnappyLoader.java:152)	at org.xerial.snappy.Snappy.(Snappy.java:46)