Android MMEX v2023.12.01.1002 release

[mickgardner1]

Great to have the Android port back - I'm currently using it on a Nokia phone, Lenovo tablet and Windows PC.

Looks like I have to manually sync from my Android devices to get it to update the database stored in my Onedrive but I can live with that.

[guanlisheng]

yup, a manual sync back is required to reflect the new database file in cloud storage. this is to avoid data conflict/loss in the early stage.

MMEX database sync.png (72.14 KiB) Viewed 239966 times

this might be the practical way today. if we change to c/s architecture to storage & manage the database in the cloud, this would be easier.
then the question would be: is it safe or ok for the end users. now, the database is 100% in your control.

[mickgardner1]

Can't see any problem with that.

[KenK]

That has fixed the deleted transaction problem, but sadly the Income vs Expenses calculation seems to have been affected - at the bottom of the Home screen it's just showing zeros, and the option under Reports shows nothing at all.

There has been another correction, download this version again and check if it is now correct.

(Sorry for taking so long to reply.) Using ammx-2023.11.27-release-v18.apk: the problem with deleted transactions and the Income vs Expenses calculations are both working correctly now.
However, the app is now crashing when I select a transaction to see the details, or when I tap the "+" to add a new transaction. There are no error messages, it just goes back to the phone's home screen. The 2023-11-24 version did the same thing. Android suggested clearing the cache for the app, but that didn't help.
I created a very small test database (on Windows, synced via OneDrive); view a transaction and add a transaction work fine with that. My main database is at transaction Id 15280.
I also tried upgrading to database v19 (using v1.7 beta on Windows and the v19 version of aMMx) and the same thing happens.

[guanlisheng]

hi @KenK ,
thanks for trying desktop v1.7-beta, it will be GA soon.

in terms of crashing while adding a new transaction, I can not reproduce it either on my dataset.
this is the most popular activity after the Main Activity, I suspect the crash is highly related to your unique dataset.
I will continue investing in the code and it would be great if you could provide a minimal dataset that can reproduce it.

[KenK]

Hi,

hi @KenK ,
I suspect the crash is highly related to your unique dataset...provide a minimal dataset that can reproduce it.

I tried using the ammx-23-11-20 release, and it's now crashing; it was working ok a week or so ago, when I noticed the deleted tx thing. Might be something I added recently.
I will try to obfuscate details in my database, then work out how to send you a copy; it's about 2MB. It might take me a few days.
Ken

[user0000]

Happy to see this again and thank you to @guanlisheng !!

I just saw that v2023.12.01.1002 released: https://github.com/moneymanagerex/andro ... 12.01.1002

I'm assuming this is out of beta?

[guanlisheng]

hi @user0000,
yes. after two weeks of running with many beta users, I think it is stable enough with some primary functionalities.

[luisdev]

There are two .apk files:

• ammx-2023.12.01-release-v18.apk

• ammx-2023.12.01-release.apk

What is the difference between those two files?

[guanlisheng]

v18 for desktop mmex v1.6.x with schema v18 while the other is for the latest destkop mmex v1.7.0/schema v19.

[luisdev]

v18 for desktop mmex v1.6.x with schema v18 while the other is for the latest destkop mmex v1.7.0/schema v19.

Thanks. So, if I am running the latest versions on MMX Windows:

• Version: 1.7.0-Beta.1 64-bit
• Built on: Dec 1 2023 08:36:46
• Database version: 19 (aes128cbc)

And MMX Android:
• Version 2023.12.01 (1002)

Should I be using ammx-2023.12.01-release.apk?

[guanlisheng]

exactly.
And thank you for trying both desktop v1.7 and android v2023.12.01

[Bingbong26]

Hello so I'm trying to use this and I have a couple of questions:

1) I saw an earlier comment that said upon opening the android app you have to select synchronize to pull the latest file from your cloud server. What happens if this is forgotten and I begin making edits, then synchronize? Will that create a conflict? If this is all true then it seems like a major problem and something that should automated (sync upon opening app and/or switching back to the app)

2) I also saw several posts stating that access owncloud/nextcloud, you click open database, then "other", then "navigate to the one drive". When I select open, on Android mmex, it just opens to my file explorer. There is nothing that says other. I could from my file explorer, navigate to nextcloud (see picture attached) and my database, and I've done this and it brings me back to the main select a database screen with no changes and no error message.

Would appreciate some guidance or answers to the above two questions points of discussion. Thank you!

Android 13
Pixel 4a
Calyxos 4.15.0
Microg disabled
Apk installed via github "ammx-2023.12.01-release.apk"

[Renato]

Perhaps this will answer your questions: viewtopic.php?p=24420#p24420

[Bingbong26]

Yes that confirms everything that I said regarding having to synchronize it whenever you open it and before you close it. Which is a showstopper for me as that is just begging for conflicts or lost data. Its.amatter of when not if.

It's instructions for how to open it are the same that I described and was unable to figure out. Mainly selection "other". My screenshot shows there is no "other" to choose.

This latest release says it supports nextcloud but I don't see how that's the case. I appreciate the efforts nonetheless. If this would have fit what I was looking for, I would have surely donated as I've been waiting for an open source budget tool that can host the database on a self hosted solution like nextcloud, that both my spouse and I can access and modify.

[guanlisheng]

May I have your owncloud/nextcloud app version in your android phone? Just wanted to understand whether they support android’s SAF

[Bingbong26]

Nextcloud 3.26.0 from fdroid.

[Renato]

https://help.nextcloud.com/t/nextcloud- ... ict/170342
https://github.com/nextcloud/android/issues/11974

[Bingbong26]

So I just realized that I CAN open it now. I don't know why it was failing before but it works now.

But is it still true that whenever you reopen the app you have to:

Reopen the database even if it's already open
Manually Synchronize before editing
Manually synchronizing when done editing

?

[guanlisheng]

in terms of synchronization, your description is true.
As the app is mainly working on local copy to avoid conflicts, we are leveraging cloud storage for basic data synchronization across different devices and platforms. it just works but not perfect due to cloud storage limation.

viewtopic.php?p=24427#p24427

[Bingbong26]

I see. Unfortunately I'll have to not use this app for now. Between my wife and I sharing the same database in nextcloud, it's bound to result in a conflict when one of use forgets to synchronize after adding a transaction. It's just too risky.

Thank you and I'll keep my eye on the project for future updates should this be improved.

[guanlisheng]

that's ok.

just a reminder that multi-modifiers to database files in cloud storage (e.g. NextCloud) might result in data loss (implicitly) and/or conflicts (explicitly) as these vendors sync underlying data via its binary-diff.

The typical and classic way is to set up a C/S architecture, saying running a real database service on somewhere.

[KenK]

I will try to obfuscate details in my database

I have now done this, sort of. I have tried it with the 2023-12-01 build of the app, and it is still crashing as before, when trying to add or view a tx. I tried both v18 and v19 versions. ("Check db schema" for v19 says there's a table missing: SETTINGS_V1_USAGE_V1.)

Having read the descriptions of the synchronisation processes needed, there's too much scope for me to mess it up, and I won't be using the Android port. So, I will leave this thread now.

[guanlisheng]

Thanks for following up, both SETTINGS_V1 and USAGE_V1 are not used in Android mmex.

In terms of synchronization, understand both your and @Bingbong26 's thought.
there is still some room to improve the UX, e.g.auto-sync periodically. we'll see

[user0000]

Maybe auto-sync on app open and close?

On the old 2019 version I was syncing the db directly which eliminated this.

Where is the cached db stored in the 2023 version?