android 集成之后上架App 市场失败

核心库在App启动就获取设备mac地址 和 应用安装列表，导致上架应用市场失败、建议修改为可延迟初始化核心库
`
尊敬的开发者，您好，请参考如下调用栈定位修复问题，谢谢。

"stackTrace":["cn.jiguang.f.a.l(Unknown Source:59)","cn.jiguang.f.a.k(Unknown Source:24)","cn.jiguang.f.a.j(Unknown Source:0)","cn.jiguang.f.a$5.b(Unknown Source:4)","cn.jiguang.s.d.a(Unknown Source:103)","cn.jiguang.f.a.g(Unknown Source:17)","cn.jiguang.br.b.a(Unknown Source:103)","cn.jiguang.bh.c.f(Unknown Source:21)","cn.jiguang.bh.c.b(Unknown Source:14)","cn.jiguang.bh.h.e(Unknown Source:24)","cn.jiguang.bh.h.a(Unknown Source:42)","cn.jiguang.bh.h.a(Unknown Source:27)","cn.jiguang.bh.h.a(Unknown Source:32)","cn.jiguang.bq.b.run(Unknown Source:9)","java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)","java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)","java.lang.Thread.run(Thread.java:929)"]

"stackTrace":["android.app.ApplicationPackageManager.getInstalledPackages(ApplicationPackageManager.java:886)","cn.jiguang.ar.d.c(Unknown Source:13)","cn.jiguang.ar.d.a(Unknown Source:0)","cn.jiguang.ar.d$1.b(Unknown Source:6)","cn.jiguang.s.d.a(Unknown Source:103)","cn.jiguang.ar.d.b(Unknown Source:68)","cn.jiguang.ar.a.a(Unknown Source:16)","cn.jiguang.ar.f.b(Unknown Source:13)","cn.jiguang.ar.e.c(Unknown Source:77)","cn.jiguang.ar.e$a.a(Unknown Source:39)","cn.jiguang.o.e.run(Unknown Source:9)","java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)","java.util.concurrent.FutureTask.run(FutureTask.java:266)","java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)","java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)","java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)","java.lang.Thread.run(Thread.java:929)"]
`

Start by tracing the Android initialization paths represented in the supplied stack traces, especially the calls involving ApplicationPackageManager.getInstalledPackages and device MAC address access. Confirm when these calls occur during app startup and identify the initialization boundary they use. Done means the core library no longer performs these accesses at startup and the reported app-market submission failure is resolved.