[eDrive] worker issue after update
- /e/ version: 1.20.0-beta & eDrive 1.4.0
- Device model(s): FP4
- Developer mode enabled: yes
- Device rooted: yes
- Trackers blocker enabled: yes
Summary
After update eDrive, some workers doesn't work properly or aren't scheduled.
The problem
Steps to reproduce Add account on a version X
Update eDrive apk to version X+1
Wait for sync
What is the current behavior?
eDrive doesn't work after an update
What is the expected correct behavior? After update, eDrive works like after a fresh install
Technical informations
How to check registered workers:
- type:
adb shell am broadcast -a "androidx.work.diagnostics.REQUEST_DIAGNOSTICS" -p "foundation.e.drive"
- type:
adb logcat | grep 'WM-DiagnosticsWrkr'
Then you'll see the list of workers, enqueued (waiting for execution), recently completed workers and running.
Example
03-14 16:06:36.086 3056 5493 I WM-DiagnosticsWrkr: Recently completed work:
03-14 16:06:36.086 3056 5493 I WM-DiagnosticsWrkr:
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: Id Class Name Job Id State Unique Name Tags
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 2a063858-b9ae-4f74-be1e-3223dfddbd36 foundation.e.drive.synchronization.SyncWorker null SUCCEEDED syncWorker foundation.e.drive.synchronization.SyncWorker,eDrive
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 48451794-bc1e-44de-ae15-98b079f45cf4 foundation.e.drive.periodicScan.FullScanWorker null FAILED fullScan foundation.e.drive.periodicScan.FullScanWorker,eDrive
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 06755003-ed4e-4f24-a76f-7dc4611e4a16 foundation.e.drive.periodicScan.ListAppsWorker null SUCCEEDED fullScan foundation.e.drive.periodicScan.ListAppsWorker,eDrive
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 10a9d50e-a8bb-4cc7-a07a-5d61c229676b foundation.e.drive.periodicScan.ListAppsWorker 16 SUCCEEDED foundation.e.drive.periodicScan.ListAppsWorker,eDrive
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 9054fd6c-361b-40a6-904c-02235af78bc8 foundation.e.drive.account.setup.FinishSetupWorker null SUCCEEDED foundation.e.drive.account.setup.FinishSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: f038352b-da73-4cc9-9c29-4b6000e6f780 foundation.e.drive.account.setup.RootFolderSetupWorker null SUCCEEDED foundation.e.drive.account.setup.RootFolderSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 037f104e-1391-44cc-8ac4-92131c20b5cb foundation.e.drive.account.setup.RootFolderSetupWorker null SUCCEEDED foundation.e.drive.account.setup.RootFolderSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 74c4d6dd-3542-4660-abd6-21398ae02357 foundation.e.drive.account.setup.RootFolderSetupWorker null SUCCEEDED foundation.e.drive.account.setup.RootFolderSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 505bca4e-ca93-4080-8211-b47731bc1eae foundation.e.drive.account.setup.RootFolderSetupWorker null SUCCEEDED foundation.e.drive.account.setup.RootFolderSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 5be606a5-60e2-43c2-af19-5cfd05fa2f53 foundation.e.drive.account.setup.RootFolderSetupWorker null SUCCEEDED foundation.e.drive.account.setup.RootFolderSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 3e7b870e-d1f9-49f5-ba6b-7f9e4fc92275 foundation.e.drive.account.setup.RootFolderSetupWorker null SUCCEEDED foundation.e.drive.account.setup.RootFolderSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: debc8e01-0e14-410e-938e-16e825a00670 foundation.e.drive.account.setup.RootFolderSetupWorker 6 SUCCEEDED foundation.e.drive.account.setup.RootFolderSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: d9f17311-16e9-4460-8e00-558971185be2 foundation.e.drive.account.setup.RootFolderSetupWorker 5 SUCCEEDED foundation.e.drive.account.setup.RootFolderSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 74c3198a-bbbf-47e7-b620-6b80dd3f2069 foundation.e.drive.account.setup.RootFolderSetupWorker null SUCCEEDED foundation.e.drive.account.setup.RootFolderSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: 12e3987d-07ca-453e-a494-95878ee19365 foundation.e.drive.account.setup.RootFolderSetupWorker null SUCCEEDED foundation.e.drive.account.setup.RootFolderSetupWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: c03da56b-5b2c-4401-bd0b-8924736fc077 foundation.e.drive.account.AccountUserInfoWorker null SUCCEEDED foundation.e.drive.account.AccountUserInfoWorker,eDrive,eDrive-init
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr: Running work:
03-14 16:06:36.115 3056 5493 I WM-DiagnosticsWrkr:
03-14 16:06:36.116 3056 5493 I WM-DiagnosticsWrkr: Id Class Name Job Id State Unique Name Tags
03-14 16:06:36.116 3056 5493 I WM-DiagnosticsWrkr: eb559471-f76d-48bb-8b39-0265baafa9a3 androidx.work.impl.workers.DiagnosticsWorker 71 RUNNING androidx.work.impl.workers.DiagnosticsWorker
03-14 16:06:36.116 3056 5493 I WM-DiagnosticsWrkr: Enqueued work:
03-14 16:06:36.116 3056 5493 I WM-DiagnosticsWrkr:
03-14 16:06:36.119 3056 5493 I WM-DiagnosticsWrkr: Id Class Name Job Id State Unique Name Tags
03-14 16:06:36.119 3056 5493 I WM-DiagnosticsWrkr: dede3c2e-b66c-425a-a1fd-d6e5ded21a2d foundation.e.drive.periodicScan.PeriodicScanWorker 53 ENQUEUED periodicScanWork foundation.e.drive.periodicScan.PeriodicScanWorker,eDrive
03-14 16:06:36.119 3056 5493 I WM-DiagnosticsWrkr: b7b3271b-82bb-4645-8b4d-1d5df96fdbc1 foundation.e.drive.account.AccountUserInfoWorker 68 ENQUEUED AccountUserInfoWorker foundation.e.drive.account.AccountUserInfoWorker,eDrive
03-14 16:06:36.119 3056 5493 I WM-DiagnosticsWrkr: 3dac45ee-e66c-403a-b488-f79316451ae0 foundation.e.drive.account.AccountUserInfoWorker 69 ENQUEUED foundation.e.drive.account.AccountUserInfoWorker,eDrive,eDrive-init
Solutions
Workaround
Possible fixes
/label typeBug
Edited by Vincent Bourgmayer