Describe the bug
When exporting payments, export worker uses payment.time - This is a LocalDateTime object which is converted to string and written as it is. This causes issues when importing as the ImportWorker expects all time to be in millis.
To Reproduce
Steps to reproduce the behavior:
Go to Backup & Sync
Export payments (with patients if required)
Clear app data
Go to Backup & Sync again
Import the payments which were exported in step 2
The payments will fail to import
Expected behavior
Payments should be imported without failure.
Additional context
Changing payment.time to payment.time.toEpochMilli() fixes the bug.
Describe the bug When exporting payments, export worker uses
payment.time
- This is a LocalDateTime object which is converted to string and written as it is. This causes issues when importing as the ImportWorker expects all time to be in millis.To Reproduce Steps to reproduce the behavior:
Expected behavior Payments should be imported without failure.
Additional context Changing
payment.time
topayment.time.toEpochMilli()
fixes the bug.