MMEX Discussion Forum

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?

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) ?

Motorola one hyper - android 11

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

Just tried from github. Not working yet.

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

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.

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.

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.

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...