Page 1 of 3

Unable to sync db after update 2025.01.03?

Posted: Thu Jan 23, 2025 6:10 pm
by ivandaudt
Hi guys. It's me again. Didn't give up yet (but close).

Looking further on the issue, I can confirm there's a problem updating the local database with its google drive equivalent on android.

I use linux and launch mmex via script, where rclone updates the local db before the app is lauched and immediately updates it after its closed.

I'm prety sure these are exact copies, as you can see on:
ivan@nbpositivo:~$ ls -l ~/Documentos/fin*
-rw-rw-r-- 1 ivan ivan 278528 jan 22 14:55 /home/ivan/Documentos/financas-ecovila.mmb
ivan@nbpositivo:~$ rclone lsf --format=pt drive:'ecovila olimpia' | grep fin
financas-ecovila.mmb;2025-01-22 14:55:55
On android, I get a "db is updated" msg, but it's clearly not, as you can see on categories screenshots on pc vs mobile.
This phone is not rooted, so I can't check further on the db.
Attached, db screenshot + logcat.

Hope it helps.

Don't know what else to do.
It's nice to think on a mobile + pc experience, but given the situation it's more like one OR other.

Re: Unable to open or create db after update 2025.01.03

Posted: Thu Jan 23, 2025 11:29 pm
by guangong
Thanks @ivandaudt, the sync is upon the database file's mtime.

seems your concern is why pc/desktop mmex modified the database itself. I think you can check the file's modified time before and after via -t
if the above is true, the android mmex behavior is expected.

Re: Unable to open or create db after update 2025.01.03

Posted: Fri Jan 24, 2025 2:27 pm
by ivandaudt
The following test process was executed to verify changes/updates passing from pc to mobile:
1- db updated fm gdrive to local desktop
2- changes on categories in mmex desktop app
3- app closed on desktop
4- db updated fm local desktop to gdrive (mtime shown above)
5- mobile app opened on android
6- db "reopened" on mobile to get latest changes

The result was: changes were not reflected on mobile.

Re: Unable to open or create db after update 2025.01.03

Posted: Fri Jan 24, 2025 3:20 pm
by guangong
I understand your issue now and I misread your categories screenshots.

what's your synchronization setting here as the 5&6 might not trigger the sync.

btw, i would like to split the thread into a different one.

Re: Unable to sync db after update 2025.01.03?

Posted: Sat Jan 25, 2025 1:40 pm
by ivandaudt
Ok. Go ahead and open a new thread so we can focus on the android synch problem.
I see an opportunity to improve UX, as the path to have your stuff in synch is not intuitive or clear.
Awaiting for yr return.

Re: Unable to sync db after update 2025.01.03?

Posted: Sat Jan 25, 2025 1:44 pm
by ivandaudt
Forgot to mention I started the whole thing on dropbox with same results.
After some attempts switched to gdrive, assuming dbox could be the problem.
And here we are...

Re: Unable to sync db after update 2025.01.03?

Posted: Sat Jan 25, 2025 1:54 pm
by guangong
To be clear, we are waiting for your synchronization settings

Re: Unable to sync db after update 2025.01.03?

Posted: Sat Jan 25, 2025 2:00 pm
by ivandaudt
Synch settings (screenshot in pt-br):
- Upd interval: 10min
- force download
- force upload
- synch on start: true
- only on wifi: false
- reset

FYI - I forced download and got the "X bytes copied"... old categories are still there... logcat attached

Re: Unable to sync db after update 2025.01.03?

Posted: Sat Jan 25, 2025 10:03 pm
by guangong
These settings and operations seem ok.

Can you try adding a transaction to verify whether it is a sync issue or a pure category behavior case?

Re: Unable to sync db after update 2025.01.03?

Posted: Mon Jan 27, 2025 12:02 pm
by ivandaudt
Did that already. And that was the critical point to raise the issue.
The following transaction (attached & using new categories) never showed up on mobile.
And considering the whole db is a single file, if one update goes, everything else goes as well, right?
So it's not a problem inside the db. It is THE db file itself that is never updated/replaced.