-
Notifications
You must be signed in to change notification settings - Fork 103
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
Save / Sync error using cloud provider Seafile pro #222
Comments
Thank you for the detailed report!
The error returned by the system is the same in your case and in #144, this is the same issue. As mentioned in #144, the problem is reproducible with other iOS apps working with Seafile iOS file provider. So it looks like this belongs to haiwen/seafile-iOS#314 — there is not much I can do to resolve it on KeePassium's side… |
@keepassium - What are the criteria to add it to your “supported/ tested” list? I’m not sure which change of the App, either Keepassium or Seafile introduced the change. Since I opened the issue, the only changes have been the iOS and App versions, everything else in the infrastructure, i.e. server hasn’t changed. I have been using it to sync my Keepass .kdbx between IPhone, IPad, Ubuntu & Windows (both SeaDrive and KeePassXC). Even over WAN using Wireguard. Only had an issue once, the current status (re-read before write/update) from file API could not be determined by Keepassium (just happened once in 2 months). .kdbx file integrity was never at risk. |
@thejoker8814 , thank you for the update!
It's rather vaguely defined as someone confirming it works, and nobody stating otherwise :) I have added Seafile Pro to the list now. Thanks again! |
@keepassium - been my pleasure (keepassium is the best iOS App for using Keepass! The least I can do is giving you a quick feedback. To be thorough, the working environment ( and as I said been using it for months with auto-app updates): Device: iPhone Xs |
Description
I've created a new Passwords.kdbx (for testing purposes) on my PC using KeePassXC and stored it on Seafile (SeaDrive for Windows). Opening it in KeePassium via iOS Files (Seafile Pro) is no problem. The bug/ issue occurs once I made changes to the .kdbx, for example creating a new entry and submitting the change via "done". KeePassium throws an error.
The most curious part is, the changes are saved and are synchronized properly to the seafile server, once you select "Save as..." in the error dialog. You don't even need to save it, just opening the dialog is enough to get it properly saved and synchronized!
How to reproduce
Steps to reproduce the behavior:
--> Error "Cannot save file (Seafile Pro)"
Result: .kdbx is stored properly, changes are reflected on the server and can be viewed in KeePassXC almost immediately.
Expected behavior
Save and Sync utilizing Seafile pro without error, because it seems to be possible without issues on the file provider side.
Environment:
Additional context
Found issue #144 which seems similar, but was never really resolved. All the linked issues do not apply, Seafile is properly configured and works without any issues.
All entries in the test Passwords.kdbx (see screenshot "KeepassXC_results") have been created within KeePassium using the same steps/ procedure.
Attachments
Step 6. result/ error dialog
KeePassium_Error_Dialog.img
Step 8. Save_as_dialog
Result in KeePassXC on PC
KeepassXC_results
KeePassium_log.txt
The text was updated successfully, but these errors were encountered: