Wrong database path about android-money-manager-ex HOT 6 CLOSED

there is an assumption that *.mmb is not encrypted, saying leave password empty/blank.

from android-money-manager-ex.

Also seeing this error on Android.

Note: I've even tried tapping the menu and going to load database and inputing the password, but I still get the looping error message.

I feel that the expected UX here would be for the app to prompt for the password to decrypt the db when you load it after it has been stopped, but I would settle for anything that would get my db to load after the very first time I create it.

Edit:

Found a workaround: Create a db that has a blank password (unencrypted). If you want your real data to be encrypted, make another db that's encrypted and keep all your data in there. Then you need to either make sure that the unencrypted db is the last one open before closing the app, or upon opening the app again, open the fake (unencrypted) db, then reopen your real (encrypted) db at which time you'll be prompted for the password. As I mentioned, ideal UX would be to be prompted for the password on startup (if the db is encrypted).

from android-money-manager-ex.

thanks @reaffirm, there is much room for uex.

1. for unencrypted files, please use *.mmb suffix and leave the password blank.
2. for the encrypted one, please use *.emb suffix and set your password.

from android-money-manager-ex.

@guanlisheng, when I do that then when I reopen the *.emb file, it's just blank and doesn't have the accounts I set up. Is there some save button I have to press before closing it?

from android-money-manager-ex.

reopening the app should be sufficient. while reopening the file means force pulling from the remote.

sync and setting -> sync will be helpful here.

from android-money-manager-ex.

hi @shay4567 , closing this and feel free to re-open

from android-money-manager-ex.