-
-
Notifications
You must be signed in to change notification settings - Fork 283
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
Could not save database with PCloud #788
Comments
The problem comes from the content-provider of the file manager application (here PCloud). |
I just tested and indeed, the behavior of PCloud is not as expected. So I advise you to download the file from PCloud, modify it from the Download folder and then re-download it in PCloud once the changes have been made. I write the note in the wiki. |
I understand that it's not because of KeepassDX that this does not work and that file sharing is not in the scope of this project, but it would be great to find a solution. Having European hosted and encrypted file sharing to sync the database would be really nice. I could try reaching out to pCloud, if you could provide a little more information what the exact problem is. |
My understanding was that pCloud was allowing external applications to get a file in read only mode. |
If simply looking for a solution, there are at least two:
|
|
Unfortunately, KeePass2Android has the same issue |
No, it doesn't. It supports WebDAV and has been working beautifully for years. |
KeePass2Android directly integrates the Pcloud API, which I don't want for several reasons that I mentioned here and in the wiki. If PCloud knowingly blocks requests to open files for writing, it's to use their API. This is a method I deplore and I won't play this game, I want KeePassDX to remain an editor not a code aggregator for external file manager. KeePass2Android integrates them, but not KeePassDX for good reasons, we just don't have the same way of seeing things, and that's why I made this app. I will maybe do an external file manager with these APIs with plugins but I'd rather devote myself to important issues than finding workarounds for companies that block the functionality of their apps. |
Just FYI, WebDAV is not a "fashionable protocol". It's been around for 24 years. |
I have nothing against WebDAV, on the contrary, it is a good protocol. But I want to keep the principle of encapsulation., it is a protocol for information transfer that requires internet (and internet permission). KeePassDX is only a file editor and not a file manager, WebDAV must be integrated in a file manager, that's all. |
Everybody wants WebDAV and Cloud integration, which I understand very well, it just takes time to create a correct file manager that manages the protocol with a content provider. It is not a lasting solution to provide a strong link between the two concepts in a single application when it would give much more advantages to separate them and do this in a dedicated app. |
I contacted pcloud about this issues. I wrote "KeepassDX" in my email and even liked to this issue, so I am not sure if it is a mix-up or typo that they wrote Keepass (with DX) in their reply. |
I don't see the connection with the European region at all... If their PCloud application doesn't work with European accounts it has nothing to do with KeePassDX, they just have to fix their servers. It must be a generic support answer that doesn't bother to look at the content provider of their app. But it is in their interest to avoid the question, they want us to integrate their API in our app. |
I am not an expert at all on this topic, but I set up Joplin to sync with pCloud via webdav. There you have to use different urls depending on the region, i.e. |
Joplin must integrate the corresponding API directly into their code, it is indicated on their website. |
I replied to their last response, this is what they said: Since KeepassDX is a third party application, it hasn't been tested with pCloud. Sometimes files can not be edited when in the pCloud app so you have to download them locally, edit and upload the new file to pCloud. Which is basically point 5) for your list above ;) If you have more details already available on what specifically PCloud needs to change about the behavior of their app , I am happy to follow up with them. They seem to be pretty responsive. I can also try helping in other ways to make it work, if you could point me towards where to start :) |
Thank you for your investment, it is appreciated.
I don't know what they need to change, the PCloud app is not open source. I will look at the subject later when making the new separate file manager application dedicated to KeePassDX. |
Thank you! I will try looking more into it and learning more about it. Let me know if I can help with anything specifically. |
As this issue is linked to an external API, I close this issue, you can continue to discuss on the FileSync application dedicated to file synchronization. Kunzisoft/FileSync#6 |
I suspect this issue was fixed in d217b52. You may want to try with KeePassDX 3.4.0+ to see if it works. |
Describe the bug
On Android 10, when opening database from a third-party application using the file picker, any attempt to edit database entries or create database entries results in an Could not save database error.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The new entry is saved successfully.
** Keepass Database **
KeePassDX (please complete the following information):
Android (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: