为什么 Jetpack WorkManager 会反复调用 doWork()？

分类：编程问答

如何解决为什么 Jetpack WorkManager 会反复调用 doWork()？

问题描述

当使用WorkManager执行唯一任务时，在doWork()发生错误并且处理异常为Result.failure()后，会再次调用doWork()。

我尝试通过日志文件排查错误，发现setComponentEnabled(context,SystemJobService.class,true);的{​​{1}}被调用了两次。 androidx.work.impl.Schedulers#createBestAvailableBackgroundScheduler 是一个单例对象，不会被调用两次。所以我很困惑。

日志

WorkManagerImpl

场景

我需要执行一个每次打开应用只执行一次的任务来上传我的统计数据，如果没有网络，就缓存它。

我的环境

jetpack workmanager 2.4.0

我的代码

应用程序.java

01-15 15:25:01.198  7797  7797 D WM-PackageManagerHelper: androidx.work.impl.background.systemjob.SystemJobService enabled
01-15 15:25:01.198  7797  7797 D WM-Schedulers: Created SystemJobScheduler and enabled SystemJobService
01-15 15:25:01.208  7797  7847 D WM-ForceStopRunnable: Performing cleanup operations.
01-15 15:25:01.303  7797  7851 D WM-PackageManagerHelper: androidx.work.impl.background.systemalarm.RescheduleReceiver enabled
01-15 15:25:01.319  7797  7851 D WM-SystemJobScheduler: Scheduling work ID b278a34c-aeeb-4c88-8f29-71b9c23e0954 Job ID 68
01-15 15:25:01.327  7797  7851 D WM-GreedyScheduler: Starting work for b278a34c-aeeb-4c88-8f29-71b9c23e0954
01-15 15:25:01.334  7797  7858 D WM-Processor: Processor: processing b278a34c-aeeb-4c88-8f29-71b9c23e0954
01-15 15:25:02.742  7797  7797 D WM-WorkerWrapper: Starting work for my_package.service.StatisticsService
01-15 15:25:02.822  7797  7847 D WM-WorkerWrapper: my_package.service.StatisticsService returned a Failure {mOutputData=Data {}} result.
01-15 15:25:02.829  7797  7847 I WM-WorkerWrapper: Worker result FAILURE for Work [ id=b278a34c-aeeb-4c88-8f29-71b9c23e0954,tags={ my_package.service.StatisticsService } ]
01-15 15:25:02.842  7797  7847 D WM-PackageManagerHelper: androidx.work.impl.background.systemalarm.RescheduleReceiver disabled
01-15 15:25:02.847  7797  7797 D WM-SystemJobService: onStartJob for b278a34c-aeeb-4c88-8f29-71b9c23e0954
01-15 15:25:02.847  7797  7847 D WM-GreedyScheduler: Cancelling work ID b278a34c-aeeb-4c88-8f29-71b9c23e0954
01-15 15:25:02.862  7797  7851 D WM-Processor: Work b278a34c-aeeb-4c88-8f29-71b9c23e0954 is already enqueued for processing
01-15 15:25:02.868  7797  7851 D WM-Processor: Processor stopping background work b278a34c-aeeb-4c88-8f29-71b9c23e0954
01-15 15:25:02.869  7797  7851 D WM-WorkerWrapper: Work interrupted for Work [ id=b278a34c-aeeb-4c88-8f29-71b9c23e0954,tags={ my_package.service.StatisticsService } ]
01-15 15:25:02.883  7797  7851 D WM-PackageManagerHelper: androidx.work.impl.background.systemalarm.RescheduleReceiver disabled
01-15 15:25:02.884  7797  7851 D WM-WorkerWrapper: WorkSpec {WorkSpec: b278a34c-aeeb-4c88-8f29-71b9c23e0954} is already done. Not interrupting.
01-15 15:25:02.884  7797  7851 D WM-Processor: WorkerWrapper interrupted for b278a34c-aeeb-4c88-8f29-71b9c23e0954
01-15 15:25:02.884  7797  7851 D WM-StopWorkRunnable: StopWorkRunnable for b278a34c-aeeb-4c88-8f29-71b9c23e0954; Processor.stopWork = true
01-15 15:25:02.899  7797  7797 D WM-Processor: Processor b278a34c-aeeb-4c88-8f29-71b9c23e0954 executed; reschedule = false
01-15 15:25:02.900  7797  7797 D WM-SystemJobService: b278a34c-aeeb-4c88-8f29-71b9c23e0954 executed on JobScheduler
01-15 15:25:02.900  7797  7797 D WM-SystemJobService: onStopJob for b278a34c-aeeb-4c88-8f29-71b9c23e0954
01-15 15:25:02.903  7797  7847 D WM-Processor: Processor stopping background work b278a34c-aeeb-4c88-8f29-71b9c23e0954
01-15 15:25:02.903  7797  7847 D WM-Processor: WorkerWrapper could not be found for b278a34c-aeeb-4c88-8f29-71b9c23e0954
01-15 15:25:02.904  7797  7847 D WM-StopWorkRunnable: StopWorkRunnable for b278a34c-aeeb-4c88-8f29-71b9c23e0954; Processor.stopWork = false

// Here doWork() is repeated once.

01-15 15:25:04.511  7923  7923 D WM-PackageManagerHelper: androidx.work.impl.background.systemjob.SystemJobService enabled
01-15 15:25:04.511  7923  7923 D WM-Schedulers: Created SystemJobScheduler and enabled SystemJobService
01-15 15:25:04.519  7923  7985 D WM-ForceStopRunnable: Performing cleanup operations.
01-15 15:25:04.600  7923  7989 D WM-PackageManagerHelper: androidx.work.impl.background.systemalarm.RescheduleReceiver enabled
01-15 15:25:04.616  7923  7989 D WM-SystemJobScheduler: Scheduling work ID 07bddcf0-33c3-43c5-ad2b-0dcb1f200e18 Job ID 69
01-15 15:25:04.624  7923  7989 I WM-GreedyScheduler: Ignoring schedule request in non-main process
01-15 15:25:04.633  7797  7797 D WM-SystemJobService: onStartJob for 07bddcf0-33c3-43c5-ad2b-0dcb1f200e18
01-15 15:25:04.634  7797  7851 D WM-Processor: Processor: processing 07bddcf0-33c3-43c5-ad2b-0dcb1f200e18
01-15 15:25:04.650  7797  7797 D WM-WorkerWrapper: Starting work for my_package.service.StatisticsService
01-15 15:25:04.697  7797  7847 D WM-WorkerWrapper: my_package.service.StatisticsService returned a Failure {mOutputData=Data {}} result.
01-15 15:25:04.700  7797  7847 I WM-WorkerWrapper: Worker result FAILURE for Work [ id=07bddcf0-33c3-43c5-ad2b-0dcb1f200e18,tags={ my_package.service.StatisticsService } ]
01-15 15:25:04.704  7797  7847 D WM-PackageManagerHelper: androidx.work.impl.background.systemalarm.RescheduleReceiver disabled
01-15 15:25:04.704  7797  7797 D WM-Processor: Processor 07bddcf0-33c3-43c5-ad2b-0dcb1f200e18 executed; reschedule = false
01-15 15:25:04.705  7797  7797 D WM-SystemJobService: 07bddcf0-33c3-43c5-ad2b-0dcb1f200e18 executed on JobScheduler
01-15 15:25:04.713  7797  7847 D WM-GreedyScheduler: Cancelling work ID 07bddcf0-33c3-43c5-ad2b-0dcb1f200e18
01-15 15:25:04.718  7797  7847 D WM-Processor: Processor stopping background work 07bddcf0-33c3-43c5-ad2b-0dcb1f200e18
01-15 15:25:04.719  7797  7847 D WM-Processor: WorkerWrapper could not be found for 07bddcf0-33c3-43c5-ad2b-0dcb1f200e18
01-15 15:25:04.719  7797  7847 D WM-StopWorkRunnable: StopWorkRunnable for 07bddcf0-33c3-43c5-ad2b-0dcb1f200e18; Processor.stopWork = false

统计服务.java

// Start a background only task.
StatisticsService.startService(getApplicationContext());

解决方法

您正在将您的 WorkRequest 作为具有 ExistingWorkPolicy.APPEND_OR_REPLACE 政策的独特作品排入队列。这意味着如果已经有另一个待处理的请求，新的请求会附加到现有的请求中，从而创建一个工作链。
替换部分仅在之前的工作失败时使用。

创建工作链，一旦正确执行了一个worker，就会执行链中的下一个。这在 WorkManager's documentation 中有解释。

另一种方法是使用 ExistingWorkPolicy.KEEP 策略，以便只将一个 WorkRequest 加入队列。

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 dio@foxmail.com 举报，一经查实，本站将立刻删除。

相关推荐

导入项目后报错问题
依赖报错 idea导入项目后依赖报错，解决方案：https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错：更换其他版本 无法下载依赖可参考：https://blog.csdn.net/weixin_42628809/a
idea不能识别yaml文件
使用mybatis plus常见错误
错误1：代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
gradle常见问题与错误
错误1：gradle项目控制台输出为乱码 # 解决方案：https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
Mybatis Plus传入参数0不起作用
错误还原：在查询的过程中，传入的workType为0时，该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
linux中make编译源码包失败
报错如下，gcc版本太低 ^ server.c:5346:31: 错误：‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
微服务启动错误：Command line is too long. Shorten command line for
解决方案1 1、改项目中.idea/workspace.xml配置文件，增加dynamic.classpath参数 2、搜索PropertiesComponent，添加如下 <property name="dynamic.classpath" value="tru
vue常见错误
删除根组件app.vue中的默认代码后报错：Module Error (from ./node_modules/eslint-loader/index.js): 解决方案：关闭ESlint代码检测，在项目根目录创建vue.config.js，在文件中添加 module.exports = { lin
spark常见错误
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
matplotlib报错：AttributeError: module 'backend_interagg' has no attribute 'FigureCanvas'. Did you mean: 'FigureCanvasAgg'?
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
gitlab登录失败，报错：This challenge page was accidentally cached by an intermediary and is no longer available.
设置时间 控制面板
后端开发常见错误
错误1：Request method ‘DELETE‘ not supported 错误还原：controller层有一个接口，访问该接口时报错：Request method ‘DELETE‘ not supported 错误原因：没有接收到前端传入的参数，修改为如下 参考 错误2：cannot r
docker常见错误
错误1：启动docker镜像时报错：Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法：重启docker -> systemctl r
idea常见错误
错误1：private field ‘xxx‘ is never assigned 按Altʾnter快捷键，选择第2项 参考：https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2：启动时报错，不能找到主启动类 #
pip安装依赖失败
报错如下，通过源不能下载，最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
maven常见错误
错误1：maven打包报错 错误还原：使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
cloud项目中常见错误
错误1：服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
springboot常见错误
错误1：运行项目后报如下错误 解决方案 报错2：Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案：在pom.
springmvc拦截器中使用redisTemplate报空指针异常
参考 错误原因 过滤器或拦截器在生效时，redisTemplate还没有注入 解决方案：在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
vite报错：npm ERR! command C:WINDOWSsystem32cmd.exe /d /s /c C:UsersychenAppDataLocalTempnpx-dde1c848.cmd
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-
pythonJavaScriptjavaHTMLPHPreactjsC#AndroidCSSNode.jssqlrpython-3.xMysqLjQueryc++pandasFlutterangularIOSdjangolinuxswifttypescript路由器JSON路由器设置无线路由器h3c华三华三路由器设置华三路由器电脑软件教程arraysdocker软件图文教程Cvue.jslaravelspring-boot