buttercup-mobile
buttercup-mobile copied to clipboard
buttercup
[WebDAV] Pathing issue: application crash after entering the archive name on android
Hi,
When you try to open an archive the android app asks you for an archive name (dunno what this is) and no matter what you do (cancel, ok, empty value, ...) the app crashes.
Please include more detail - it's impossible to discern what's happening with the current info. What version of Android, what phone, etc.. This is the first we've heard of it so it is possible it's an isolated issue. We need to work out, if that is the case, why in your case it's not working.
Hi,
I use a oneplus 5 with android 8.1 and my file is on a dropbox account.
The steps to reproduce it are: -add an archive -open dropbox (+log in) -select the file -enter the file password (ok) -enter the file name (crash after hitting ok)
the only feedback I have is android asking me to reopen the app.
I have the same issue on IPHONE. Iphone 7, latest IOS. 11.3.something.
-Add archive using webdav. It connects fine @ https://mynas.mynasprovicer.com:5001/Passwordlocation -Shows folder with DB file. Choose DB file. passwordfile.bcup Archive password: Accepts fine. Archive name: "PasswordDB"
I get this message.
Error: Failed adding archive Failed adding source: Authentication failed - possible tampering
Background:
Migrated from keepass a few weeks ago, and it works generally quite well. - I am able to connect using webdav from chrome from an external location without any problems.
It was working perfectly with my phone for about a week, but for the last 2 weeks I have been getting this message. I have tried removing and adding the DB several times, until I found this message.
Question: Does the archive name determine anything apart from the name on the local device?
@Sblop your issue is different, I'm afraid.. most likely #78.
I have tried removing and adding the DB several times
Try editing the archive on desktop and make a small change.. the newly saved archive should work on mobile. This is unfortunately a known issue which we're trying to fix as we speak.
Does the archive name determine anything apart from the name on the local device?
No, nothing apart from how it appears on the device.
@irazers Very weird. I'm sorry I don't have any great suggestions right now as this is the first time I've heard of such an issue. By any chance is the file name or archive name weird in any way, or does it contain any characters outside the range a-z0-9_-? Obviously there shouldn't be character encoding issues with characters outside that range, but it's a good place to start.
ok so I've tested with a bran new file create with the mobile app and it works perfectly.
Something must come from the archive itself but the archive has no problems with the desktop app
This may be partly related to #78, but I'm not 100% sure. We're in the process of updating the crypto processes in the app to combat issues like that. Hopefully it helps for this issue as well.
I might have found something: try to add an archive with subfolders tree in it and it crashes.
@irazers Really sorry about the delay on this. I guess you may have moved on, but in case you can remember, were there any special characters in the path? If it's not private, could you possibly share it?
Hi,
Yes my file is private. I will try to create one from scratch to reproduce the problem
@irazer I don't mean your archive, sorry, but the file path. If it's not too secret sharing it might help (if there are spaces or special characters in some order).. It's possible the file path also causes an issue.
Sharing a test archive that fails on your device would also be helpful, of course. Thanks!
I created a empty library in the same folder and it works fine
A small comment though: there is no possibility to remove an archive from the archive list which is very annoying
there is no possibility to remove an archive from the archive list which is very annoying
@irazer There is actually - If you swipe left on a vault in the list, an option to remove it is made visible.
@irazer I asked earlier but perhaps you misunderstood my request - I was hoping that you might be able to sure the path your archive is stored at. It could be that this is due to the filename you're writing to. If there are folders in your path you would not like to share publicly, please consider contacting me via my keybase account.
Ok the problem was indeed coming from the path itself it was containing this letter 'é' I changed it and now it works
Ok the problem was indeed coming from the path itself it was containing this letter 'é' I changed it and now it works
@irazer That's great! This means we have a clear issue we can address. We'll definitely get this fixed as soon as possible. Thanks for the help!
Is this still an issue? We've had many updates to the WebDAV library since 2018.