本文介绍了是否有针对目标API 26或更高版本的firebase-dispatcher库的更新?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近收到警告,要求从Google Play控制台将Android目标版本更新为26或更高.但是,我已经将目标SDK设置为26.

I recently get the warning to update the Android Target Version to 26 or more from the Google Play Console. However, I have already set the target SDK to 26.

我检查了项目中包含的所有库的AndroidManifest文件和合并清单.

I check the AndroidManifest file and the merged manifest for all the libraries I have included in the project.

清单来源下的库很少,而在其他清单文件(包含在合并中,但未提供任何元素)-这是什么意思?

There are few libraries which are under Manifest Sources and few are under theOther manifest files(Included in merge, but did not contribute any elements) - what does this mean?

我可以仅将清单更新为该项目的目标API 26,并上载清单以查看清单是否被接受.

Can i update the manifest to target API 26 for this project only and upload the to see if it gets accepted or not.

Google需要验证该应用程序的短信和通话记录权限,但是当我将该应用程序上载到Play商店时,会收到警告-•

Google needs to verify the App for SMS and Call Log permission but when i upload the app to the play store i get the warning - •

推荐答案

它称为现在的工作管理器 Firebase Job-Dispatcher 可能不再收到更新./p>

it's called WorkManager now; the Firebase Job-Dispatcher might not receive updates anymore.

implementation "android.arch.work:work-firebase:1.0.0-alpha11"
androidTestImplementation ("android.arch.work:work-testing:1.0.0-beta01") {
    exclude group: "android.arch.work"
}

仅应用程序包的API级别很重要-运行时权限需要发挥作用-SMS和呼叫日志"的这些关键权限除外,这些权限需要审核.最近,即使我仅使用SIP电话,也有来自美国境内的安装,该审查可能如此.可能有人从应用程序发送高级短信,从而迅速扣除预付额度-或提供带有电话号码的robocall服务来打扰您.同样,smartTAN取决于SMS.攻击媒介是现实的,因此进行这些检查是有原因的.

only the API level of the application package matters - and the run-time permissions need to function - except these critical permissions for SMS and Call Log, which are subject to review. recently had one install from US territory, which might have been such review, even if I only use SIP telephony. there might have been people sending premium SMS from apps, which quickly deduct prepaid credits - or providing robocall services with phone numbers to bother. also smartTAN depends on SMS. the attack vector is realistic, therefore these checks are in place for a reason.

这篇关于是否有针对目标API 26或更高版本的firebase-dispatcher库的更新?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-26 17:43
查看更多