Android MMEX v2023.12.01.1002 release

[Bingbong26]

I've had got it miss luck with sync thing. 5 years ago it completely deleted my data somehow. I had the rules setup correctly. Ever since then, since I couldn't identify what I had done wrong, I lost trust in it.

But perhaps I'll give that a whirl. Still doesn't solve the manual sync requirement to save the database file. Unless the sync is just to push it to the cloud option. I thought even the local copy was only updated when you select sync in the app.

[guangong]

I just updated Syncthing to the vote thread (it seems it reset the historical data...)

Unless the sync is just to push it to the cloud option.

this is exactly today's sync behavior. if we compare it with git, sort of `git push --force`

btw, I will take a look at the android mmex to work on the remote database directly, then each change will be reflected in cloud storage immediately.
as
1. the SQLite3 database file is small, (e.g. less than 2MB)
2. the modification frequency should be pretty low (e.g. less than 10 times per day),
3. especially when there are only a couple of devices and platforms that share the same database file.

I think it would work most of the time as physical conflicts would be rare.

[guangong]

all

just rolled another beta release https://github.com/moneymanagerex/andro ... 12.06.1003
enabling auto-sync of the last opened database on app open if there is no conflict.
to mitigate current issue by an extra app open
@Bingbong26 , @user0000 , and @KenK , appreciated if you can have a try.

[luisdev]

Thank you!

I'm not sure what to test with regards to this change:
"enabling auto-sync of the last opened database on app open if there is no conflict"

What auto-sync are you referring to? Is it to sync the MMX Android database to a cloud provider (like DropBox, OneDrive, etc.)?

[guangong]

Is it to sync the MMX Android database to a cloud provider (like DropBox, OneDrive, etc.)?

yup. just like click `menu->synchronize` on app start.

[Bingbong26]

Just tried it out. After updating I opened the app, immediately added a transaction, then closed the app (swiped away in recent apps) without pressing the sync button. Reopened the app and it hung for about 5 seconds but once it loaded it displayed thebnitirocation that the remote database has been updated, and I saw the nextcloud upload symbol pop up in my system tray/nototication bar.

Tried it with my wife's phone using the same database. Made a transaction and closed the app. Tried on my phone but it wasn't updated because she hadn't reopened the app on hers to force the sync. Even after she reopened her app, I have to reopen the database file (sync won't pull down the updated version, says no changes locally so it won't sync).

[guangong]

you might need to wait a while for NextCloud to perform the sync after your wife reopens her app.
The sync is bi-directional and would pull down in this case. next time you can click `menu-> synchronize` to double verify.

btw, as your wife's phone using the same database, did you see the new transaction added from your phone?

[Bingbong26]

Yes when I added a new transaction from my phone, then reopened the app to push it to the dB, when I opened it on my wife's app it did show the transaction I made. We'll just have to ensure we're either manually pressing sync after adding a transaction or closing and reopening the app to ensure the database is updated/synced.

In the event where one of us doesn't sync a change (forget to close and reopen or manually sync) and the other person makes adds a different transaction and syncs, will that cause a conflict once hers eventually tries to sync?

[guangong]

the basic function is working as
1. your wife's app had the transaction you made.
3. after force pull (via open database), you can see the transaction your wife made.

both are positive. in terms of synchronize, it might be some metadata error from either NextCloud or MMEX, saying to determine the last modification time for both remote and local database.

[guangong]

In the event where one of us doesn't sync a change (forget to close and reopen or manually sync) and the other person makes adds a different transaction and syncs, will that cause a conflict once hers eventually tries to sync?

Yes, it will result in conflicts today as the cloud storage sync is on file level instead of transaction level.