Closed rfc2822 closed 3 weeks ago
Maybe the accounts are not active in safe mode, although the content provider is active (and then deletes all orphaned address books)?
@ArnyminerZ Are there adb logs when booting into safe mode? Do you have any other idea how to find out what happens?
Rebooted to safe mode after having synchronized the contacts. If querying them through ADB this is the response:
$ adb shell content query --uri content://com.android.contacts/raw_contacts
No result found.
Booting back to the device, as reported, did not show any contacts, neither on ADB:
$ adb shell content query --uri content://com.android.contacts/raw_contacts
No result found.
nor the contacts app. The addressbook is there, but it's empty:
After synchronizing, all the contacts are back.
No rellevant logs are found in DAVx⁵, no strange sync works or anything.
Same here. On my physical test device (Samsung Galaxy A30) booting into safe mode actually removed all DAVx5 accounts too. After booting into normal mode the accounts were all restored, but the contacts are gone.
I did ask ChatGPT if this is possible, just to see if he/she/it had any clues, and said that it might happen because accounts added by third-party apps are not considered "system accounts" (whatever that means), and they are considered cache, and removed automatically.
I tried with the contacts sync baked into google play services and contacts stored in google accounts are not deleted when rebooting into safe mode.
We just got to make DAVx5 a system app, then we're good :P
Would probably solve the battery exemption, work quota and long running work / foreground notification problems too. Would be interesting to know whether this happens on devices with /e/ OS where DAVx5 operates as system app?
Have also tried again. Seems that rebooting into safe mode
After another reboot, DAVx5 may start again, and the account is there, but the contacts are gone. The sync state is stored in the contacts DB, too (not in the account), so at the next sync, the contacts are re-synced.
@devvv4ever Should we document this in the manual and/or an FAQ?
In the FAQ would be also good I guess! But let's do this if people still write about that in the future and if they don't find the answer in the manual.
We should see
Discussed in https://github.com/bitfireAT/davx5-ose/discussions/1038