Sync fail after upgrade to 2.5.1 (Arch)

[drasnor]

On Arch, I upgraded the onedrive-abraunegg client to version 2.5.1and am now encountering an error that appears to relate to timestamp parsing when I attempt to sync:

~/OneDrive $ onedrive --sync --verbose
No user or system config file found, using application defaults
Using 'user' configuration path for application config and state data: /home/user/.config/onedrive
D-Bus message bus daemon is available; GUI notifications are now enabled
Using IPv4 and IPv6 (if configured) for all network operations
Attempting to contact Microsoft OneDrive Login Service
Successfully reached Microsoft OneDrive Login Service
Checking Application Version ...
Attempting to initialise the OneDrive API ...
Configuring Global Azure AD Endpoints
The OneDrive API was initialised successfully
Opening the item database ...
BAD TIMESTAMP (REGEX FAIL): 2023-06-14T09:06:56.606Z
WARNING: Invalid timestamp provided by the Microsoft OneDrive API: 2023-06-14T09:06:56.606Z
Application Version:  onedrive v2.5.1
Account Type:         personal
Default Drive ID:     79df50edc488b7e7
Default Root ID:      79DF50EDC488B7E7!107
Remaining Free Space: 1.10 GB (1181116006 bytes)
Sync Engine Initialised with new Onedrive API instance
All application operations will be performed in the configured local 'sync_dir' directory: /home/user/OneDrive
Fetching /delta response from the OneDrive API for Drive ID: 79df50edc488b7e7
Processing API Response Bundle: 1 - Quantity of 'changes|items' in this bundle to process: 210
BAD TIMESTAMP (REGEX FAIL): 2024-09-27T22:51:52.1877232Z
Attempting to perform a database vacuum to optimise database
Database vacuum is complete
core.exception.AssertError@src/itemdb.d(725): The DB record mtime entry is not a valid ISO timestamp entry. Please attempt a --resync to fix the local database.
----------------
??:? _d_assert_msg [0x55d3956c4590]
??:? itemdb.Item itemdb.ItemDatabase.buildItem(sqlite.Statement.Result) [0x55d39568ace2]
??:? bool itemdb.ItemDatabase.selectById(const(char)[], const(char)[], out itemdb.Item) [0x55d395688abe]
??:? void syncEngine.SyncEngine.processRootAndDeletedJSONItems(std.json.JSONValue, immutable(char)[], bool, bool, bool) [0x55d395651b21]
??:? void syncEngine.SyncEngine.processDeltaJSONItem(std.json.JSONValue, ulong, int, ulong, bool) [0x55d395651191]
??:? void syncEngine.SyncEngine.fetchOneDriveDeltaAPIResponse(immutable(char)[], immutable(char)[], immutable(char)[]) [0x55d39564f26b]
??:? void syncEngine.SyncEngine.syncOneDriveAccountToLocalDisk() [0x55d39564cf6c]
??:? void main.performStandardSyncProcess(immutable(char)[], monitor.Monitor) [0x55d395508167]
??:? _Dmain [0x55d395505380]

I attempted a resync as instructed which did not resolve the issue. The timestamp appears to be in ISO 8601 format.

~/OneDrive $ onedrive --sync --verbose --resync
No user or system config file found, using application defaults
Using 'user' configuration path for application config and state data: /home/user/.config/onedrive
D-Bus message bus daemon is available; GUI notifications are now enabled

The usage of --resync will delete your local 'onedrive' client state, thus no record of your current 'sync status' will exist.
This has the potential to overwrite local versions of files with perhaps older versions of documents downloaded from OneDrive, resulting in local data loss.
If in doubt, backup your local data before using --resync

Are you sure you wish to proceed with --resync? [Y/N] Y

Deleting the saved application sync status ...
Using IPv4 and IPv6 (if configured) for all network operations
Attempting to contact Microsoft OneDrive Login Service
Successfully reached Microsoft OneDrive Login Service
Checking Application Version ...
Attempting to initialise the OneDrive API ...
Configuring Global Azure AD Endpoints
The OneDrive API was initialised successfully
Opening the item database ...
BAD TIMESTAMP (REGEX FAIL): 2023-06-14T09:06:56.606Z
WARNING: Invalid timestamp provided by the Microsoft OneDrive API: 2023-06-14T09:06:56.606Z
Application Version:  onedrive v2.5.1
Account Type:         personal
Default Drive ID:     79df50edc488b7e7
Default Root ID:      79DF50EDC488B7E7!107
Remaining Free Space: 1.10 GB (1181116006 bytes)
Sync Engine Initialised with new Onedrive API instance
All application operations will be performed in the configured local 'sync_dir' directory: /home/user/OneDrive
Fetching /delta response from the OneDrive API for Drive ID: 79df50edc488b7e7
Processing API Response Bundle: 1 - Quantity of 'changes|items' in this bundle to process: 210
BAD TIMESTAMP (REGEX FAIL): 2024-09-27T22:46:57.2179148Z
Attempting to perform a database vacuum to optimise database
Database vacuum is complete
core.exception.AssertError@src/itemdb.d(725): The DB record mtime entry is not a valid ISO timestamp entry. Please attempt a --resync to fix the local database.
----------------
??:? _d_assert_msg [0x5cdd9cf1c590]
??:? itemdb.Item itemdb.ItemDatabase.buildItem(sqlite.Statement.Result) [0x5cdd9cee2ce2]
??:? bool itemdb.ItemDatabase.selectById(const(char)[], const(char)[], out itemdb.Item) [0x5cdd9cee0abe]
??:? void syncEngine.SyncEngine.processRootAndDeletedJSONItems(std.json.JSONValue, immutable(char)[], bool, bool, bool) [0x5cdd9cea9b21]
??:? void syncEngine.SyncEngine.processDeltaJSONItem(std.json.JSONValue, ulong, int, ulong, bool) [0x5cdd9cea9191]
??:? void syncEngine.SyncEngine.fetchOneDriveDeltaAPIResponse(immutable(char)[], immutable(char)[], immutable(char)[]) [0x5cdd9cea726b]
??:? void syncEngine.SyncEngine.syncOneDriveAccountToLocalDisk() [0x5cdd9cea4f6c]
??:? void main.performStandardSyncProcess(immutable(char)[], monitor.Monitor) [0x5cdd9cd60167]
??:? _Dmain [0x5cdd9cd5d380]

The upgrade to client version 2.5.1 was pulled in during a larger system update and I did not do any preparatory steps prior to allowing the package manager (yay) to pull in the updated package from AUR. I can't confirm whether I am upgrading from 2.5.0 or 2.4.25 as I'm not sure when the last time I ran a system update was. My first clue that I had an issue was when I rebooted following the update and the systemd onedrive service was continuously restarting. Any tips for resolving this issue?

[abraunegg]

The v2.5.1 release is broken - sorry.

I cannot fix until Monday.

Downgrade or build v2.5.0 manually

[drasnor]

No worries, thanks for the quick reply.

[drasnor]

I successfully downgraded to v2.5.0 using the older PKGBUILD per the instructions on the Arch wiki and the client is once again syncing without error.

[drasnor]

First, you need to obtain the PKGBUILD from the AUR commit (near "download" in the first link above):

1. Download the AUR commit tarball (direct download link)
2. Extract the AUR commit tarball (tar -xvf aur-644abc2de6fb06a28d70eb75a6b91077e4b1b58a.tar.gz)

Next, you need to build the package

1. Run 'makepkg' with no args in the directory extracted from the commit tarball (e.g. aur-644abc2de6fb06a28d70eb75a6b91077e4b1b58a)

Finally, install the package. Use the filename of the package file that makepkg produced

1. sudo pacman -U onedrive-abraunegg-2.5.0-1-your_arch_here.pkg.tar.zst

[limbsjones]

tanx!!! worked like a charm!!!

[Heidmall]

I had removed my message so as not to disturb you, but you saw it and replied, so thank you very much.
Unfortunately for me I think I have another problem, so I will wait patiently until monday
Have a good weekend

~/workspace/aur-644abc2de6fb06a28d70eb75a6b91077e4b1b58a$ makepkg
downloading required keys...
:: Import PGP key 77193F152BDBE6A6, "Arch Linux ARM Build System builder+seattle@archlinuxarm.org"? [Y/n]
error: key "77193F152BDBE6A6" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)