极光推送java.lang.UnsatisfiedLinkError:错误的解决
2014-06-05 16:30
453 查看
做项目的时候接手之前的代码,用到极光推送,报了个错误
06-05 16:13:03.460: E/CrashHandler(12406): java.lang.ExceptionInInitializerError
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.service.ServiceInterface.a(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.api.JPushInterface.init(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): at com.cardapp.hoshk.MyApplication.onCreate(MyApplication.java:29)
06-05 16:13:03.460: E/CrashHandler(12406): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:999)
06-05 16:13:03.460: E/CrashHandler(12406): at com.lbe.security.service.core.client.internal.InstrumentationDelegate.callApplicationOnCreate(InstrumentationDelegate.java:168)
06-05 16:13:03.460: E/CrashHandler(12406): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4208)
06-05 16:13:03.460: E/CrashHandler(12406): at android.app.ActivityThread.access$1300(ActivityThread.java:136)
06-05 16:13:03.460: E/CrashHandler(12406): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1261)
06-05 16:13:03.460: E/CrashHandler(12406): at android.os.Handler.dispatchMessage(Handler.java:99)
06-05 16:13:03.460: E/CrashHandler(12406): at android.os.Looper.loop(Looper.java:137)
06-05 16:13:03.460: E/CrashHandler(12406): at android.app.ActivityThread.main(ActivityThread.java:4803)
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.reflect.Method.invokeNative(Native Method)
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.reflect.Method.invoke(Method.java:511)
06-05 16:13:03.460: E/CrashHandler(12406): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
06-05 16:13:03.460: E/CrashHandler(12406): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
06-05 16:13:03.460: E/CrashHandler(12406): at dalvik.system.NativeStart.main(Native Method)
06-05 16:13:03.460: E/CrashHandler(12406):<span style="color:#ff0000;"> Caused by: java.lang.UnsatisfiedLinkError: Couldn't load jpush: findLibrary returned null</span>
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.Runtime.loadLibrary(Runtime.java:365)
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.System.loadLibrary(System.java:535)
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.service.PushProtocol.<clinit>(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): ... 16 more
06-05 16:13:03.460: E/CrashHandler(12406): java.lang.UnsatisfiedLinkError: Couldn't load jpush: findLibrary returned null
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.Runtime.loadLibrary(Runtime.java:365)
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.System.loadLibrary(System.java:535)
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.service.PushProtocol.<clinit>(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.service.ServiceInterface.a(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.api.JPushInterface.init(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): at com.cardapp.hoshk.MyApplication.onCreate(MyApplication.java:29)
出错的代码为:
.so文件,一看原代码果然没有添加。
于是便下载了最新版jpush-sdk-release1.6.1的sdk,拷贝libjpush.so放入,重刷之后还是报错,我就纳闷了。
紧接着上了极光问答的社区,搜索了这个问题,发现解决方法还是一样,问题是 .so文件不一样了,libsys.so文件也有,libpushp**.so之类的文件也有,这才意识到版本不同,对应的.so文件也不一样。
最后,拷贝了新的jpush-sdk-release1.6.1.jar替代了原来的jpush-sdk-release1.5.5.jar,再刷一次,程序终于不报错了
所以结论就是,原因是.so不在正确的位置(libs–>armeabi–>.so),且要jar包和.so文件要对应,只要拷贝好正确的文件和位置,就没问题了
06-05 16:13:03.460: E/CrashHandler(12406): java.lang.ExceptionInInitializerError
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.service.ServiceInterface.a(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.api.JPushInterface.init(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): at com.cardapp.hoshk.MyApplication.onCreate(MyApplication.java:29)
06-05 16:13:03.460: E/CrashHandler(12406): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:999)
06-05 16:13:03.460: E/CrashHandler(12406): at com.lbe.security.service.core.client.internal.InstrumentationDelegate.callApplicationOnCreate(InstrumentationDelegate.java:168)
06-05 16:13:03.460: E/CrashHandler(12406): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4208)
06-05 16:13:03.460: E/CrashHandler(12406): at android.app.ActivityThread.access$1300(ActivityThread.java:136)
06-05 16:13:03.460: E/CrashHandler(12406): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1261)
06-05 16:13:03.460: E/CrashHandler(12406): at android.os.Handler.dispatchMessage(Handler.java:99)
06-05 16:13:03.460: E/CrashHandler(12406): at android.os.Looper.loop(Looper.java:137)
06-05 16:13:03.460: E/CrashHandler(12406): at android.app.ActivityThread.main(ActivityThread.java:4803)
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.reflect.Method.invokeNative(Native Method)
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.reflect.Method.invoke(Method.java:511)
06-05 16:13:03.460: E/CrashHandler(12406): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
06-05 16:13:03.460: E/CrashHandler(12406): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
06-05 16:13:03.460: E/CrashHandler(12406): at dalvik.system.NativeStart.main(Native Method)
06-05 16:13:03.460: E/CrashHandler(12406):<span style="color:#ff0000;"> Caused by: java.lang.UnsatisfiedLinkError: Couldn't load jpush: findLibrary returned null</span>
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.Runtime.loadLibrary(Runtime.java:365)
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.System.loadLibrary(System.java:535)
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.service.PushProtocol.<clinit>(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): ... 16 more
06-05 16:13:03.460: E/CrashHandler(12406): java.lang.UnsatisfiedLinkError: Couldn't load jpush: findLibrary returned null
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.Runtime.loadLibrary(Runtime.java:365)
06-05 16:13:03.460: E/CrashHandler(12406): at java.lang.System.loadLibrary(System.java:535)
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.service.PushProtocol.<clinit>(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.service.ServiceInterface.a(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): at cn.jpush.android.api.JPushInterface.init(Unknown Source)
06-05 16:13:03.460: E/CrashHandler(12406): at com.cardapp.hoshk.MyApplication.onCreate(MyApplication.java:29)
出错的代码为:
JPushInterface.setDebugMode(true); <span style="color:#ff0000;"> JPushInterface.init(this);</span>后来搜素了极光帮助文档Java.lang.UnsatisfiedLinkError后,发现问题在于libs/armeabi/
.so文件,一看原代码果然没有添加。
于是便下载了最新版jpush-sdk-release1.6.1的sdk,拷贝libjpush.so放入,重刷之后还是报错,我就纳闷了。
紧接着上了极光问答的社区,搜索了这个问题,发现解决方法还是一样,问题是 .so文件不一样了,libsys.so文件也有,libpushp**.so之类的文件也有,这才意识到版本不同,对应的.so文件也不一样。
最后,拷贝了新的jpush-sdk-release1.6.1.jar替代了原来的jpush-sdk-release1.5.5.jar,再刷一次,程序终于不报错了
所以结论就是,原因是.so不在正确的位置(libs–>armeabi–>.so),且要jar包和.so文件要对应,只要拷贝好正确的文件和位置,就没问题了
相关文章推荐
- 关于使用极光推送报 java.lang.ClassNotFoundException: com.google.gson.Gson”错误记录
- 自行集成极光推送所遇到的一个错误::java.lang.UnsatisfiedLinkError:
- java.lang.OutOfMemoryError: Java heap space 错误解决方法
- java.lang.OutOfMemoryError:PermGen space错误解决方法(收集、转)
- 解决 java/lang/NoClassDefFoundError: java/lang/Object 错误
- java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver 错误的解决办法
- java.lang.UnsupportedClassVersionError的错误解决
- 如何解决 tomcat 下 oracle 缓冲池 读取 clob 字段内容 时的错误 "java.lang.ClassCastException: org.apache.commons.dbcp.DelegatingResultSet "
- Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/helpers/NOPLoggerFactory"错误解决方
- 错误:java.lang.NoClassDefFoundError: org/objectweb/asm/CodeVisitor的解决方法
- 错误:java.lang.NoClassDefFoundError: org/objectweb/asm/CodeVisitor的解决方法
- MAVEN2使用mvn install命令出现java.lang.OutOfMemoryError错误解决办法
- Zend Studio for Eclipse的java.lang.NullPointerException错误的解决方法
- 解决android集成环境ADT的java.lang.NullPointerException错误
- "Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/helpers/NOPLoggerFactory"错误解决方法
- 错误解决:java.lang.ClassCastException: org.apache.xerces.dom.DeferredDocumentImpl
- java.lang.NoSuchFieldError: EMPTY_LIST,EMPTY_MAP错误的解决方法
- Eclipse 报 “Exception in thread "main" java.lang.OutOfMemoryError: Java heap space ”错误的解决办法
- java.lang.NoSuchMethodError 错误的解决方法
- 安装BIEE时,启动setup.exe后,出现java.lang.NoClassDefFoundError:run错误的解决办法