【错误记录】360 加固后的运行错误 ( 加固 SO 动态库时不能对第三方动态库进行加固 )
生活随笔
收集整理的這篇文章主要介紹了
【错误记录】360 加固后的运行错误 ( 加固 SO 动态库时不能对第三方动态库进行加固 )
小編覺得挺不錯的,現在分享給大家,幫大家做個參考.
文章目錄
- 一、加固 SO 動態庫報錯
- 二、解決方案
一、加固 SO 動態庫報錯
在 【Android 安全】使用 360 加固寶加固應用 ( 購買高級加固服務 | 設置資源加固 | 設置 SO 文件保護配置 | 設置 SO 防盜用文件配置 | 反編譯驗證加固效果 ) 加固時 , 遇到的問題 ;
使用 360 加固保 加固 SO 動態庫后 , 一旦調用該 SO 庫所在的類 , 就會報如下錯誤 ;
2021-04-27 14:10:01.605 611-1808/? E/SurfaceFlinger: size mismatch (1920, 1080) > (1080, 1920) 2021-04-27 14:10:02.991 2578-2578/xxx E/crashsdk: load libcrashsdk.so failed! 2021-04-27 14:10:03.063 2578-2594/xxx E/JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)java.lang.UnsatisfiedLinkError: JNI_ERR returned from JNI_OnLoad in "/data/app/xxx-AwEPOi3u8iBcwz7sxpy0zw==/lib/arm64/libxxx.so"at java.lang.Runtime.loadLibrary0(Runtime.java:1016)at java.lang.System.loadLibrary(System.java:1669)at xxx.<clinit>(xxx.java:57)at xxx.xxx(Unknown Source:0)at xxx.xxxxxxService$xxx.xxx(xxx.java:99)at xxx.xxxxxxPlayer$Stub.onTransact(xxx.java:158)at android.os.Binder.execTransact(Binder.java:731) 2021-04-27 14:10:03.063 2578-2594/xxx E/AndroidRuntime: FATAL EXCEPTION: Binder:2578_3Process: xxx:xxx, PID: 2578java.lang.UnsatisfiedLinkError: JNI_ERR returned from JNI_OnLoad in "/data/app/xxx-AwEPOi3u8iBcwz7sxpy0zw==/lib/arm64/libxxx.so"at java.lang.Runtime.loadLibrary0(Runtime.java:1016)at java.lang.System.loadLibrary(System.java:1669)at xxx.<clinit>(xxx.java:57)at xxx.xxx(Unknown Source:0)at xxx.xxxxxxService$xxx.xxx(xxx.java:99)at xxx.xxxxxxPlayer$Stub.onTransact(xxx.java:158)at android.os.Binder.execTransact(Binder.java:731) 2021-04-27 14:10:03.064 2578-2594/xxx E/DEBUG: begin to generate java report 2021-04-27 14:10:03.072 2578-2594/xxx E/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 2021-04-27 14:10:03.073 2578-2594/xxx E/DEBUG: Basic Information: 'pid: 2578/tid: 2594/time: 20210427141003' 2021-04-27 14:10:03.076 2578-2594/xxx E/DEBUG: Cpu Information: 'abi: arm64-v8a,armeabi-v7a,armeabi/processor: AArch64 Processor rev 1 (aarch64)/hardware: Qualcomm Technologies, Inc MSM8998' 2021-04-27 14:10:03.077 2578-2594/xxx E/DEBUG: Mobile Information: 'model: Pixel 2/version: 9/sdk: 28' 2021-04-27 14:10:03.077 2578-2594/xxx E/DEBUG: Build fingerprint: 'google/walleye/walleye:9/PQ3A.190801.002/5670241:user/release-keys' 2021-04-27 14:10:03.078 2578-2594/xxx E/DEBUG: Runtime Information: 'start: 20210427141002/maxheap: 201326592/primaryabi: arm64-v8a/ground: bg' 2021-04-27 14:10:03.078 2578-2594/xxx E/DEBUG: Application Information: 'version: 0.1/subversion: release/buildseq: 82f731d1/versioncode: 1' 2021-04-27 14:10:03.079 2578-2594/xxx E/DEBUG: CrashSDK Information: 'version: 3.2.0.4/nativeseq: 0/javaseq: 200403192109/arch: /target: umeng' 2021-04-27 14:10:03.079 2578-2594/xxx E/DEBUG: Report Name: 5f3cf3dfd3093221547aec89_0.1_82f731d1_Pixel-2_9_161950380306424305_20210427141003_bg_java.log 2021-04-27 14:10:03.088 2578-2594/xxx E/DEBUG: UUID: 8cb2c151-7c59-4cec-8534-4e4562dcb1e3 2021-04-27 14:10:03.088 2578-2594/xxx E/DEBUG: Log Type: java 2021-04-27 14:10:03.088 2578-2594/xxx E/DEBUG: Activity: (none) 2021-04-27 14:10:03.088 2578-2594/xxx E/DEBUG: --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 2021-04-27 14:10:03.089 2578-2594/xxx E/DEBUG: um_app_key: 5f3cf3dfd3093221547aec89 2021-04-27 14:10:03.089 2578-2594/xxx E/DEBUG: um_app_channel: Umeng 2021-04-27 14:10:03.089 2578-2594/xxx E/DEBUG: um_os: android 2021-04-27 14:10:03.089 2578-2594/xxx E/DEBUG: um_crash_sdk_version: v0.0.5 2021-04-27 14:10:03.089 2578-2594/xxx E/DEBUG: um_umid_header: ai191fc43f360df8ac2281730c590eae61 2021-04-27 14:10:03.089 2578-2594/xxx E/DEBUG: --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 2021-04-27 14:10:03.089 2578-2594/xxx E/DEBUG: Process Name: 'xxx:xxx' 2021-04-27 14:10:03.089 2578-2594/xxx E/DEBUG: Thread Name: 'Binder:2578_3' 2021-04-27 14:10:03.090 2578-2594/xxx E/DEBUG: Back traces starts. 2021-04-27 14:10:03.091 2578-2594/xxx E/DEBUG: java.lang.UnsatisfiedLinkError: JNI_ERR returned from JNI_OnLoad in "/data/app/xxx-AwEPOi3u8iBcwz7sxpy0zw==/lib/arm64/libxxx.so" 2021-04-27 14:10:03.091 2578-2594/xxx E/DEBUG: at java.lang.Runtime.loadLibrary0(Runtime.java:1016) 2021-04-27 14:10:03.091 2578-2594/xxx E/DEBUG: at java.lang.System.loadLibrary(System.java:1669) 2021-04-27 14:10:03.091 2578-2594/xxx E/DEBUG: at xxx.<clinit>(xxx.java:57) 2021-04-27 14:10:03.092 2578-2594/xxx E/DEBUG: at xxx.xxx(Unknown Source:0) 2021-04-27 14:10:03.092 2578-2594/xxx E/DEBUG: at xxx.xxxxxxService$xxx.xxx(xxx.java:99) 2021-04-27 14:10:03.092 2578-2594/xxx E/DEBUG: at xxx.xxxxxxPlayer$Stub.onTransact(xxx.java:158) 2021-04-27 14:10:03.092 2578-2594/xxx E/DEBUG: at android.os.Binder.execTransact(Binder.java:731) 2021-04-27 14:10:03.096 2578-2594/xxx E/DEBUG: Back traces ends. 2021-04-27 14:10:03.096 2578-2594/xxx E/DEBUG: --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 2021-04-27 14:10:03.096 2578-2594/xxx E/DEBUG: meminfo: 2021-04-27 14:10:03.097 2578-2594/xxx E/DEBUG: MemTotal: 3744240 kBMemFree: 267428 kBMemAvailable: 1390504 kBBuffers: 12852 kBCached: 1270596 kBSwapCached: 7224 kBActive: 1514192 kBInactive: 724988 kBActive(anon): 822640 kBInactive(anon): 281756 kBActive(file): 691552 kBInactive(file): 443232 kBUnevictable: 147248 kBMlocked: 147248 kBSwapTotal: 524284 kBSwapFree: 1360 kBDirty: 604 kBWriteback: 0 kBAnonPages: 1098952 kBMapped: 423192 kBShmem: 2004 kBSlab: 280836 kBSReclaimable: 96656 kBSUnreclaim: 184180 kBKernelStack: 50272 kBPageTables: 56856 kBNFS_Unstable: 0 kBBounce: 0 kBWritebackTmp: 0 kBCommitLimit: 2396404 kBCommitted_AS: 70488548 kBVmallocTotal: 258867136 kBVmallocUsed: 0 kBVmallocChunk: 0 kBCmaTotal: 196608 kBCmaFree: 0 kB二、解決方案
經過咨詢官方技術支持 , 發現加固時 , 不要加固引用的第三方動態庫 , 只加固自己編譯生成的動態 ;
總結
以上是生活随笔為你收集整理的【错误记录】360 加固后的运行错误 ( 加固 SO 动态库时不能对第三方动态库进行加固 )的全部內容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: 【Android 安全】使用 360 加
- 下一篇: 【Android Protobuf 序列