Keepass2android: 1.05-pre google drive error

[carstengrimm]

Just updated to the latest (beta) version of keepass2android and being a long time user with google drive sync. just now after the update when trying to access my database via google drive option, as well as via third party applications or file mangers to access google drive it results in toast error telling the following

the name must not be empty: null

tried a few times and my database has been working fine before...
for the time being i manually copied from drive to internal sd which works fine.

[Karreg]

Same here. Unfortunately I was in a hurry so I did not note down what was happening. However, here is how it was when it happened and how I workarounded it.

I tried to open the database from the databases history (it's the only entry, but whatever...)
I got "unable to synchronize" or whatever the error message is when network is unavailable
I try to open the database with fingerprint
The app crashes

I tried a second time, the behavior has been the same.

Then I deleted the entry from database history, tried to open it again from google drive.
I got the "the name must not be empty: null" and nothing happened.

I force closed the app, started it again, tried again to open database from google drive, and I got the same message "the name must not be empty: null", _if I remember well_. But this time I managed to browse google drive, and open the database again.

If I'm not wrong, then the message is not related to the issue. But I may not remember well as it happened yesterday, and as I said, it was a bit of an emergency :)

[carstengrimm]

force closing the app and thus trying to get another go with google drive seems to make google drive work again.

[PhilippC]

I don't have a clue why this should not work anymore (of course I believe you that it does not). Can you please check in the android settings for the app if the GET_ACCOUNTS permissions is still granted? Can anybody confirm problems when try to use system file picker (which should be totally independant from KP2A)?

[Jazzy99]

Here is what I did to solve the problem. Open Settings -> App Permissions -> Storage permissions. The slider for Keepass2Android was off. I slid that to on and all works well again. I now get the usual "Remote file and cache synchronized" again when starting app and closing database.

I hope this helps,

[PhilippC]

ok, I think I found the reason. It's a behavior change in Android 8 which I overlooked when upgrading to target sdk 26: https://developer.android.com/about/versions/oreo/android-8.0-changes.html#rmp
Will need to check possible other side effects of this and probably request a few more permissions at some places.

[Karreg]

Just to answer, once it has been fixed by either method, the issue does not appear again, so it's hard to test...

[Jazzy99]

First everyone thanks so much for the effort. I appreciate the application.
One possible suggestion on testing? Try removing app completely and
reinstall to see if behavior reproduces at the unfixed version and repeat
with fixed version. Just thinking out loud.

Best regards,

On Mon, Feb 26, 2018, 10:58 Karreg [e-mail] wrote:

Just to answer, once it has been fixed by either method, the issue does
not appear again, so it's hard to test...

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PhilippC/keepass2android/issues/265#issuecomment-368571275,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AgYKOf3IgoBrAKiqFPLrpl1VwKFe2CT6ks5tYuLDgaJpZM4SQPtA
.

[aduarte9]

Hi everyone,
I've removed the definitions from the recent opened databases (long press it and then remove), then added it again from google drive and now it's working fine.
Best regards.

[AlexWayfer]

Hi everyone,
I've removed the definitions from the recent opened databases (long press it and then remove), then added it again from google drive and now it's working fine.
Best regards.

It doesn't help, the name must not be empty: null when I tried to add new DB from Google Drive (after Google Drive selecting, before list of files).

Here is what I did to solve the problem. Open Settings -> App Permissions -> Storage permissions. The slider for Keepass2Android was off. I slid that to on and all works well again. I now get the usual "Remote file and cache synchronized" again when starting app and closing database.

I hope this helps,

The slider was off for me, I turned it on, but there was error anyway. Then I turned it off, and there is no error! Strange things.

[ninjamonkey198206]

I know this issue is considered closed, but I just had the exact same thing happen. Tried all of the above and it worked for my work Google account, but not my personal account.

I think that it's actually an issue with permissions to your Google account itself, not necessarily the app. The problem may exist in the app somewhere (losing proper configuration, or it's using outdated info after a update on Google's systems), but going online and logging into your Google account, accessing your account settings, and removing keepass2android's access permissions causes the app to request them again, which solved the problem.

It seems to be some sort of issue with whatever protocol is used or info is exchanged during the handshake to access your Drive, so unless there's a bad bit of code in the app, forcing it to re-request permissions should always solve the problem.

I didn't snoop into the network traffic or logs to verify this, but all the symptoms seem to fit.

[ninjamonkey198206]

Note: The issue only seems to exist when attempting to access a remote file via Drive, however local copies open. They wouldn't sync, though, and the same errors occured. That is what led me to believe it's an issue with Google drive permissions for the account in question, not an issue with permissions local to the device.

[ghost]

I also was affected with this issue and I had the permission for storage enabled already for keepass2android. The issue started happening randomly and it was still saving on my phone so I didn't think much about it until when loading the keepass on my computer the new entries were not included. To solve I followed @Jazzy99 suggestion and checked the permissions. Upon disabling (as it was already enabled) and re-Enabling the permission it started working and updated the remote file immediately. Not sure if this helps but just wanted to report my issue and solution. There was a system update between occurrences (One Plus 6) but I did not notice the issue until a few days ago when update was >1 week ago.

[t4k1t]

I also was affected with this issue and I had the permission for storage enabled already for keepass2android. The issue started happening randomly and it was still saving on my phone so I didn't think much about it until when loading the keepass on my computer the new entries were not included. To solve I followed @Jazzy99 suggestion and checked the permissions. Upon disabling (as it was already enabled) and re-Enabling the permission it started working and updated the remote file immediately. Not sure if this helps but just wanted to report my issue and solution. There was a system update between occurrences (One Plus 6) but I did not notice the issue until a few days ago when update was >1 week ago.

Exact same thing happened to me today.

[RufusJWB]

Same here with the latest version. Since some weeks, sync doesn't work anymore. I checked permissions, disabled and enabled storage access and now everything works again. Strange thing!

[PhilippC]

this is a duplicate of #432, please see https://github.com/PhilippC/keepass2android/issues/432#issuecomment-401561254 for how to solve the problem.