Android不混淆没问题，混淆后无法启动

2019-11-08 05:39:26 5k 阅读 AI 写同款 · GEO 优化AI 选题数据监测一键分发 ›
胜天半子 胜天半子 墨衍会员 · AI 创作全网分发 墨衍智能分发 通过墨衍一键同步至各平台 可同步平台 CSDN微信公众号微博知乎掘金百家号博客园抖音小红书 你的文章也可以这样分发 墨衍会员 ¥399起/年，写一次发全网 我也要 + 加入社区
Android 混淆那些事儿 本文主要讲述了代码混淆和资源混淆的原理，Studio默认的混淆方案，混淆的参数，以及如何对Apk进行代码混淆(自定义混淆文件)和资源混淆(结合微信混淆和美团混淆两种方案)，避免Apk被逆向。 阅读详情
2019-11-08 17:38:53.632 588-588/? E/WifiHAL: enter wifi_get_link_stats
2019-11-08 17:38:53.638 1465-1657/? E/WificondControl: Noise: 0, Snr: -1, Chload: -1
2019-11-08 17:38:53.943 754-910/? E/JankService: specialActionEntryHandler: should reset and not report
2019-11-08 17:38:53.961 1465-1946/? E/ProcessInfoCollector: getProcessInfo: failed to find this proc
2019-11-08 17:38:53.966 8089-8089/? E/.cmii.ambulanc: Not starting debugger since process cannot load the jdwp agent.
2019-11-08 17:38:53.986 2027-3003/? E/AwareLog: SPKSchedFeature: Uid has been sent, ignore.
2019-11-08 17:38:53.998 2027-3091/? E/AwareLog: GameSdkConfigReader: GameSdkLog: idNameMap: null
2019-11-08 17:38:53.999 1927-2381/? E/XEngineMpipControl: Invalid SubId
2019-11-08 17:38:53.999 1927-2381/? E/Hicom_PolicyCenterService: handleForeGroundAppChanged. INVALID_UID
2019-11-08 17:38:54.023 8089-8089/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.cmcc.cmii.ambulance, PID: 8089
java.lang.RuntimeException: Unable to instantiate application com.cmcc.cmii.app.MyApplication: java.lang.RuntimeException: Stub!
at android.app.LoadedApk.makeApplication(LoadedApk.java:1183)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6688)
at android.app.ActivityThread.access$2000(ActivityThread.java:273)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2020)
at android.os.Handler.dispatchMessage(Handler.java:112)
at android.os.Looper.loop(Looper.java:216)
at android.app.ActivityThread.main(ActivityThread.java:7625)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987)
Caused by: java.lang.RuntimeException: Stub!
at a.g.i.<init>(Unknown Source:7)
at a.g.j.<init>(Unknown Source:0)
at a.c.d.<init>(Unknown Source:1)
at com.cmcc.cmii.app.MyApplication.<init>(Unknown Source:0)
at java.lang.Class.newInstance(Native Method)
at android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:50)
at android.app.Instrumentation.newApplication(Instrumentation.java:1127)
at android.app.LoadedApk.makeApplication(LoadedApk.java:1175)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6688) 
at android.app.ActivityThread.access$2000(ActivityThread.java:273) 
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2020) 
at android.os.Handler.dispatchMessage(Handler.java:112) 
at android.os.Looper.loop(Looper.java:216) 
at android.app.ActivityThread.main(ActivityThread.java:7625) 
at java.lang.reflect.Method.invoke(Native Method) 
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524) 
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987) 
2019-11-08 17:38:54.028 754-2837/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.029 754-2837/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.030 754-2837/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.030 754-12040/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.033 754-12040/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.034 754-12040/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.039 754-12040/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.039 754-12041/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.040 754-12041/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.041 754-12041/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.041 754-12041/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.041 754-12042/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.041 754-12042/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.042 754-12042/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.042 1927-1945/? E/HsmCoreServiceImpl: onTransact in code is: 102
2019-11-08 17:38:54.043 2027-3091/? E/AwareLog: GameSdkConfigReader: GameSdkLog: idNameMap: null
2019-11-08 17:38:54.043 1927-2381/? E/Hicom_PolicyCenterService: unrecognized exception captured during handleMessage: 68 exception: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.huawei.systemserver.emcom.policycenter.policycenterservice.decisionsystem.AppLifeCycleManager.rmAppAllSocketClosed(int)' on a null object reference
2019-11-08 17:38:54.044 754-12042/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return.
2019-11-08 17:38:54.062 2027-3003/? E/AwareLog: SPKSchedFeature: Uid has been sent, ignore.
2019-11-08 17:38:54.062 1927-2381/? E/XEngineMpipControl: Invalid SubId
2019-11-08 17:38:54.083 1465-1752/? E/HiDATA_HiNetwork: monitor handleActivityChange curPkgName is com.huawei.android.launcher curUid is 10063 lastPkgName is :com.huawei.android.launcher
2019-11-08 17:38:54.083 1927-8118/? E/DollieAdapterService: notifyActivityState pkg:com.huawei.android.launcher/com.huawei.android.launcher.unihome.UniHomeLauncher state:2 fg:true mUid:10063
2019-11-08 17:38:54.092 16405-16433/? E/[HwRecSys]CandidateSetHelper: getHwCandidateByPkgAndActivity -> this pkg HwCandidates is null!
2019-11-08 17:38:54.245 730-865/? E/dubaid: [CpuHandler.cpp] findUidEntry# Uid(10286) has not package, maybe it's already uninstalled
2019-11-08 17:38:54.245 730-865/? E/dubaid: [CpuHandler.cpp] setUidCpuTime# Failed to find uid entry
2019-11-08 17:38:54.337 1465-1482/? E/ProcessInfoCollector: getProcessInfo: failed to find this proc
2019-11-08 17:38:54.627 754-3123/? E/LOGSERVER_UTILS: [Erecovery]readEvent: eRecEventManager readEvent 0
2019-11-08 17:38:55.662 754-3123/? E/LOGSERVER_UTILS: [Erecovery]readEvent: eRecEventManager readEvent 0
2019-11-08 17:38:56.646 588-588/? E/WifiHAL: enter wifi_get_link_stats
2019-11-08 17:38:56.650 1465-1657/? E/WificondControl: Noise: 0, Snr: -1, Chload: -1
2019-11-08 17:38:56.662 8109-8109/? E/JankService: child Thread receive to stop
2019-11-08 17:38:56.689 754-3123/? E/LOGSERVER_UTILS: [Erecovery]readEvent: eRecEventManager readEvent 0
2019-11-08 17:38:56.802 754-907/? E/JankService: all data read ok
2019-11-08 17:38:57.275 2255-2416/? E/HSM_Install_BG: NatTrafficNotifyService:imsi is null, so return
2019-11-08 17:38:57.729 754-3123/? E/LOGSERVER_UTILS: [Erecovery]readEvent: eRecEventManager readEvent 0
2019-11-08 17:38:58.770 754-3123/? E/LOGSERVER_UTILS: [Erecovery]readEvent: eRecEventManager readEvent 0
2019-11-08 17:38:59.261 1465-1657/? E/WificondControl: Noise: 0, Snr: -1, Chload: -1
2019-11-08 17:38:59.654 588-588/? E/WifiHAL: enter wifi_get_link_stats
2019-11-08 17:38:59.657 1465-1657/? E/WificondControl: Noise: 0, Snr: -1, Chload: -1
2019-11-08 17:38:59.791 754-3123/? E/LOGSERVER_UTILS: [Erecovery]readEvent: eRecEventManager readEvent 0
2019-11-08 17:39:00.036 1829-1829/? E/DateView: DateView,mCurrentTime: 1573205940036
...全文
android 混淆 很久没用过混淆功能了，因为之前的包都使用第三方加固了，而且项目开发好几年了，突然要混淆也很麻烦。换了家公司后，感觉还是得混淆代码才行，不然直接暴露源码也太不行了。 阅读详情

相关推荐

Android 混淆打包不混淆第三方jar包

在Android开发过程中，混淆打包是一项重要的优化技术，它有助于保护应用代码免受逆向工程的威胁，同时减少应用大小。然而，有时我们需要对第三方jar包进行特殊处理，以确保它们能在混淆后仍能正常工作。本

进来瞅瞅试试

Android SO文件保护OLLVM混淆加固——混淆篇（二）

总的来说，OLLVM混淆是提升Android应用安全性的有效手段之一，通过混淆技术，可以有效降低代码被逆向分析的风险。

不知世事

android实现一键反混淆

ProGuard是Android SDK中内置的混淆工具，它提供了预处理、优化、混淆和预校验等功能。

laughing_lh

Android studio 混淆配置详解

/libModule/proguard-rules.pro' // 设置Proguard规则文件 }}````proguard-android.txt`是Android SDK提供的默认混淆规则，一般不需要修改

weixin_38518958

Android代码混淆的写法总结

此外，保持第三方包不混淆也可以通过 `-keep` 指令来实现，例如保持支付宝包不混淆。在实际开发中，Android 代码混淆是非常重要的一步，可以保护代码的安全和 prevents 反编译。

weixin_38703295
评论 4
收藏 已收藏
分享
返回顶部
胜天半子
胜天半子
Android 80,490 成员 91,375 内容
+ 加入社区