vivo的sdk隐私合规通不过， 说是先读了AndroidID

同意后才调用插件的初始化JPush.init， 最新的隐私检测发现还是先读了AndroidID
11:34:47.797 [测试动作] 启动隐私合规检测
11:35:35.666 (SDK: 极光推送SDK)读取AndroidID
11:37:42.276 弹出隐私政策
android_id
at android.provider.Settings$Secure.getStringForUser()
at android.provider.Settings$Secure.getString(Settings.java:4664)
at cn.jiguang.commons.L.j.a(Unknown Source:10)
at cn.jiguang.commons.g.o.a(Unknown Source:164)
at cn.jiguang.commons.g.o.c(Unknown Source:33)
at cn.jiguang.commons.g.m.d(Unknown Source:62)
at cn.jiguang.commons.g.n.a(Unknown Source:39)
at cn.jiguang.commons.v.c.k(Unknown Source:144)
at cn.jiguang.commons.v.c.a(Unknown Source:159)
at cn.jiguang.commons.j.m.e(Unknown Source:7)
at cn.jiguang.f.b$b.a(Unknown Source:30)
at cn.jiguang.f.b.a(Unknown Source:15)
at cn.jiguang.f.b$a.g(Unknown Source:14)
at cn.jiguang.f.b$a.d(Unknown Source:9)
at cn.jiguang.ai.a.c(Unknown Source:147)
at cn.jiguang.ai.a.(Unknown Source:11)
at cn.jiguang.ai.a.a(Unknown Source:13)
at cn.jiguang.ab.h.a(Unknown Source:7)
at cn.jiguang.ab.h.a(Unknown Source:35)
at cn.jiguang.au.b.run(Unknown Source:9)
at cn.jiguang.au.d$1.run(Unknown Source:19)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)

测了好久发现是vivo的sdk有问题，注释掉就能通过测试了。
implementation 'cn.jiguang.sdk.plugin:huawei:6.0.1'
implementation 'cn.jiguang.sdk.plugin:xiaomi:6.0.1'
implementation 'cn.jiguang.sdk.plugin:meizu:6.0.1'
implementation 'cn.jiguang.sdk.plugin:oppo:6.0.1'
//implementation 'cn.jiguang.sdk.plugin:vivo:6.0.1'
implementation 'cn.jiguang.sdk.plugin:honor:6.0.1'

Start by reproducing the privacy check with the Vivo dependency cn.jiguang.sdk.plugin:vivo:6.0.1 enabled, comparing it with the configuration where that dependency is commented out. Trace when JPush.init runs relative to the AndroidID access shown in the stack trace; done means the Vivo plugin no longer reads AndroidID before the privacy policy is accepted.