Unable to open or create db after update 2025.01.03

[ivandaudt]

Hi there. I'm having trouble opening or creating new databases with MMEX after updating it via fdroid.
I'm currently running ver 2025.01.03.
Opening a db in google drive or creating a new db returns to the same initial screen with both buttons...
Attached a video with the process and steps involved.
Any suggestions?

[guangong]

hi @ivandaudt, may we have your device information?
we have a similar report on Redmi Note 7(Android 10)

if possible, would you try v2025.01.14 (1061) ?

[ivandaudt]

Motorola one hyper - android 11

[guangong]

ok, can you try v2025.01.14 (1061) from either GitHub or Google Store ?

[ivandaudt]

Just tried from github. Not working yet.

[guangong]

thanks and this is wired. can you share some logs?

[ivandaudt]

Downgraded to 2024.12.31 and it opens my db fm google drive w/no problems.
The issue is a different one now... (both local and remote modified, although I know it was not).
Will upgrade again to the latest and get its logs for you.

[ivandaudt]

I can still see the database after upgrading fm 2024.12.31 to 2025.01.14, but won't take the risk of closing it.

Some error pop up quickly at the app after open, which I located at the end of the log:
01-20 14:31:46.394 10061 10061 E ActivityThread: Failed to find provider info for com.google.android.apps.docs.storage
01-20 14:31:46.394 10061 10061 W DocumentFile: Failed query: java.lang.NullPointerException: Attempt to invoke interface method 'int android.database.Cursor.getCount()' on a null object reference
01-20 14:31:46.396 10061 10061 E ActivityThread: Failed to find provider info for com.google.android.apps.docs.storage
01-20 14:31:46.405 10061 10061 W DocFileMetadata: Cursor is null or empty for URI: content://com.google.android.apps.docs.storage/document/...
01-20 14:31:46.406 10061 10061 W DocFileMetadata: Cursor is null or empty for URI: content://com.google.android.apps.docs.storage/document/...
01-20 14:31:46.413 10061 10061 D FileStorageHelper: The remote file updated at 1969-12-31T21:00:00.000-0300
01-20 14:31:46.413 10061 10061 D FileStorageHelper: The remote file updated at 1969-12-31T21:00:00.000-0300

Hope it helps.

[guangong]

Thanks @ivandaudt, this is helpful.

The cloud path (`content://com.google.android.apps.docs.storage/document/...`) was not stored completely for some reason, and this caused the sync errors...

I recommend re-exporting your local database to Google Drive to avoid losing data. then re-open the exported copy from MMEX app.

+ @wolfsolver for awareness.

[ivandaudt]

Ups, sorry. Forgot to mention I removed the final target and replaced it by the "..."
The full target address is there at the original log file.
The error has nothing to do with it.

Lookig at the error trace, looks like gdrive instance is missing (null pointer + 1969 file update...)
Just a guess, but...

[guangong]

ok, understood.

your feeling is correct that the error is from opening the target Google Drive for writing via SAF, it might be due to the permission or file deletion.
can you confirm the file is still available from your Google Drive client and Files app on your phone?

in the meanwhile, previous exporting & re-open the new copy are still good to verify the case.

[ivandaudt]

Ok. Looks like we found a way around the problem.
Exported, switched, reopened it, synched and finally I got a "X bytes updated" message (and no errors)!
I'm afraid some data was lost (missed new categories and recent transactions).
Will double-check, but apparently both mobile and pc are in synch now.

Attached screenshots for your reference.

Will use it for couple of days and report on it.

[lutzarno]

I have the same problem with Huawei P20 Pro and HONOR Pad X8a.

Until version 1057 everything was ok.

I could load the datababase from my NextCloud storage and it would show all new entries added by the desktop version of MMEX.

With any version after 1057 (last I tried is 1062) the database is not updated when I open the remote database on an Android device.

If I delete my local database in /storage/emulated/0/Android/data/com.money.manager.ex/files/databases/<filename>.mmb I will not be able to create a new database locally or open a remote database with versions > 1057. MMEX stays at the screen where I only can select to create a database or to open an existing database.

Going back to 1057 resolves the issue.

[guangong]

Thanks @lutzarno for reporting this. can you share your Android OS version as well?

This is wired. Can you try out v2025.01.24 (1064) and provide any logs?

[lutzarno]

Android version of the Honor tablet is 14, the P20 Pro runs with version 10.

Updated to 1064 on my tablet. This version loads the NextCloud database and shows correct balances of the accounts in that database.

Creating a new database does still not work. I see an error message for a moment and the result of the action is not ok. I currently have no need to create a new database so it's ok for me now.

Find attached screenshots of the messages, maybe they can help to track down this issue.

[guangong]

thanks, this is super helpful. we are still investing in the issue of creating a new database.

[lutzarno]

Another App gave me a hint today when I tried to open a file: the app showed a dialog that said that I needed a file manager that accepts the actions ACTION_CREATE_DOCUMENT and ACTION_OPEN_DOCUMENT.

After re-activating the default filemanager I was able to open a file. I could also open a database in MMEX then.

[guangong]

ok. What's your file manager? and are we still talking about v2025.01.03?

[lutzarno]

This is on a Honor Pad X8a. This tablet has two preinstalled filemanagers, both called the same: "Dateien" (= Files). One of them (Google "documentsui") can be deaktivated in the settings, the other (Honor) can't. App-Info for Google app shows version 14-11814667. Seems like only this app offers the reqiured actions.

Updated to version 2025.02.02 of MMEX in the meantime to check the behaviour.

[guangong]

Thanks @lutzarno, it seems MMEX works well with the built-in Files app, I guess they share the same impl of Android Storage Access Framework (SAF).

in the meanwhile, MMEX4Android will improve its error message to make it clear. + @wolfsolver for awareness.