Fixed
Status Update
Comments
ra...@google.com <ra...@google.com> #2
That seems quite bad :/ weird.
We have fairly large test projects which do not take anywhere close to it, maybe your code is triggering some bad code path.
Can you provide a sample or share your project with us? It is impossible to do something here unless we have a reproduction case. Might also possibly be related to your machine configuration.
We have fairly large test projects which do not take anywhere close to it, maybe your code is triggering some bad code path.
Can you provide a sample or share your project with us? It is impossible to do something here unless we have a reproduction case. Might also possibly be related to your machine configuration.
ap...@google.com <ap...@google.com> #3
Let me see what I can do on the reproduction as I am anyways blocked on this. I will try to extract out the DB module in a new project and see if it reproduces the issue.
Description
Version used: 1.0.0-beta01
Devices/Android versions reproduced on: Samsung J1 (6.0.1)
I run Worker with exponential backoff strategy and 60 seconds initial delay, however worker is being executed after retry without delay (see log).
The issue is reproducible on Samsung J1 (6.0.1), and partially reproducible on emulator 6.0 (the second retry attempt is made 5 seconds after the first, then works as expected). You may refer to sample project in attachments to try to reproduce the issue.