Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libimagepipeline.so
See original GitHub issue
Fatal Exception: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libimagepipeline.so caused by: dlopen failed: "/mnt/expand/7c0f06c2-1644-460f-8533-efe2fb639ade/user/0/com.studio/lib-main/libimagepipeline.so" is 32-bit instead of 64-bit
at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SourceFile:703)
at com.facebook.soloader.SoLoader.loadLibraryBySoName(SourceFile:564)
at com.facebook.soloader.SoLoader.loadLibrary(SourceFile:500)
at com.facebook.soloader.SoLoader.loadLibrary(SourceFile:455)
at com.facebook.imagepipeline.nativecode.ImagePipelineNativeLoader.load(SourceFile:40)
at com.facebook.imagepipeline.memory.NativeMemoryChunk.(SourceFile:31)
at com.facebook.imagepipeline.memory.NativeMemoryChunkPool.alloc(SourceFile:25)
at com.facebook.imagepipeline.memory.NativeMemoryChunkPool.alloc(SourceFile:13)
at com.facebook.imagepipeline.memory.BasePool.get(SourceFile:267)
at com.facebook.imagepipeline.memory.MemoryPooledByteBufferOutputStream.(SourceFile:51)
at com.facebook.imagepipeline.memory.MemoryPooledByteBufferFactory.newByteBuffer(SourceFile:73)
at com.facebook.imagepipeline.memory.MemoryPooledByteBufferFactory.newByteBuffer(SourceFile:24)
at com.facebook.imagepipeline.cache.BufferedDiskCache.readFromDiskCache(SourceFile:373)
at com.facebook.imagepipeline.cache.BufferedDiskCache.access$400(SourceFile:35)
at com.facebook.imagepipeline.cache.BufferedDiskCache$2.call(SourceFile:193)
at com.facebook.imagepipeline.cache.BufferedDiskCache$2.call(SourceFile:174)
at bolts.Task$4.run(SourceFile:357)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at com.facebook.imagepipeline.core.PriorityThreadFactory$1.run(SourceFile:51)
at java.lang.Thread.run(Thread.java:818)
ndk {
abiFilters 'armeabi-v7a'
}
SoLoader version. [0.5.1]
I think this is relevant/cause of https://github.com/facebook/fresco/issues/2296 pls check
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
java.lang.UnsatisfiedLinkError: couldn't find DSO to load ...
Fatal Exception : java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libimagepipeline.so at com.facebook.soloader.SoLoader.
Read more >How to fix 'java.lang.UnsatisfiedLinkError: couldn't find DSO to ...
When running we run in to below exception java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libgifimage.so caused by: JNI_ERR ...
Read more >java.lang.UnsatisfiedLinkError: couldn't find DSO to load ...
Android : React-Native : java. lang. UnsatisfiedLinkError : couldn't find DSO to load : libhermes. so [ Beautify Your Computer ...
Read more >couldn't find DSO to load: libhermes.so result: 0 - Design - Adalo
my release under production status on google play is stuck because of this error : “java.lang.UnsatisfiedLinkError: couldn't find DSO to ...
Read more >I'm having problem upgrading my react native app to 64 bit
The error i got is: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libimagepipeline.so caused by: dlopen failed: "/data/data/.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@zetbrush could you tell me which version of the Android Gradle Plugin you were using? Recently we ran into a similar issue when updating from AGP
3.2.0
to3.4.0
. I found that using either AGP3.3.0
or3.4.0
would cause this crash, however3.2.0
would successfully find the .so fileIt sounds like this issue was resolved with the v0.10.3 release based on the release notes. However, I’m still getting crash reports in production for it since upgrading. I did notice though that I only had
configurations.all { resolutionStrategy { force "com.facebook.soloader:soloader:0.10.3" } }
in build.gradle and did not havedependencies { implementation "com.facebook.soloader:soloader:0.10.3+"
in app/build.gradle. Not sure if that’s an issue so I’ve since shipped that. Anyone confirm or deny 10.3 resolving the issue for them?