-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Root element is missing #1284
Comments
is this a self-maintained FTP server? Is it possible to set up a testing account for me (crocoapps@gmail.com)? |
I sent you the credentials to a ftp Account on my Server. Its a rented Webspace at a German Hoster. |
I have the same problem, file is on a FTP server. The file is synchronized (and still does fine) with KeePass 2. |
Tested and confirmed working in the Beta. Thanks @PhilippC and @mayermart ! |
thanks for testing and reporting! |
This just started happening to me. I tried to update to the latest beta and it's still going on across two devices. I'm using Nextcloud for synchronization though. I can verify that if I copy the file manually to the local device, it does open. The debug logs from the app show nothing out of the ordinary except for the eventual "Root Element is Missing" stack trace. Nextcloud seems to show reasonable web requests:
Should I open a separate issue for this one? It just started happening recently and I did notice a new update recently and it looks like I'm on |
@ikogan yes please. Please also - if possible - send a test account on your server to crocoapps@gmail.com (referencing the issue) |
Sorry I wasn't able to get to this but it does seem like it's fixed itself recently. |
After Keepass2Android was automatically updated to Version 1.08-r1 on my Mobile i can't open a Database synced via FTP.
Syncing seems to work. The Error appears after entering the Password.
On my Tablet running 1.07b-r0 i can open the same Database from the same location.
I tried to reinstall Keepass2Android and reconfigured the FTP Connection, but the error stays.
The text was updated successfully, but these errors were encountered: