Warning: file_get_contents(/data/phpspider/zhask/data//catemap/4/json/13.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Android 升级到WorkManager 2.3.4后出现ObsoletIntCustomCheck lint警告_Android_Lint_Android Workmanager - Fatal编程技术网

Android 升级到WorkManager 2.3.4后出现ObsoletIntCustomCheck lint警告

Android 升级到WorkManager 2.3.4后出现ObsoletIntCustomCheck lint警告,android,lint,android-workmanager,Android,Lint,Android Workmanager,将WorkManager从2.2.0升级到2.3.4后,我得到了一个新的ObsoleteLintCustomChecklint警告。如果我正确理解了警告消息,那么他们添加了一个使用旧API版本的新lint检查?不过,谷歌没有显示任何与WorkManagerIssueRegistry相关的有用信息 有人以前遇到过这个问题,或者知道如何解决这个问题吗 在格拉德尔: implementation "androidx.work:work-runtime-ktx:2.3.4" testImplementa

将WorkManager从2.2.0升级到2.3.4后,我得到了一个新的
ObsoleteLintCustomCheck
lint警告。如果我正确理解了警告消息,那么他们添加了一个使用旧API版本的新lint检查?不过,谷歌没有显示任何与
WorkManagerIssueRegistry
相关的有用信息

有人以前遇到过这个问题,或者知道如何解决这个问题吗

在格拉德尔:

implementation "androidx.work:work-runtime-ktx:2.3.4"
testImplementation "androidx.work:work-testing:2.3.4"

你可以忽略这一点。我们在
WorkManager 2.4.x
中修复了这个问题。很抱歉造成混淆。

目前我已在
lint.xml
中抑制了此错误,但我不希望这样做。谢谢您提供的信息。升级到2.4Wow后,我将删除忽略!有人刚把它修好,就像一个来自Goog warts的魅力工程师!美好的谢谢
Lint found an issue registry (`androidx.work.lint.WorkManagerIssueRegistry`) which is older than 
the current API level; these checks may not work correctly. Recompile the checks against the 
latest version. Custom check API version is 3 (3.3), current lint API level is 6 (3.6+)

Lint can be extended with "custom checks": additional checks implemented by 
developers and libraries to for example enforce specific API usages required by a library or a 
company coding style guideline. The Lint APIs are not yet stable, so these checks may either 
cause a performance degradation, or stop working, or provide wrong results. This warning flags 
custom lint checks that are found to be using obsolete APIs and will need to be updated to run 
in the current lint environment. It may also flag issues found to be using a **newer** version 
of the API, meaning that you need to use a newer version of lint (or Android Studio or Gradle 
plugin etc) to work with these checks.