Quantcast
Channel: keepass2android Issue Tracker Rss Feed
Viewing all 955 articles
Browse latest View live
↧

Edited Unassigned: Autofill service conflicts Google app's voice search [599]

September 24, 2016, 3:45 am
$
0
0
I have Nexus 5x using Android N.

I had noticed that I whenever I switched to Google app home screen or the phone's home screen,
then in the search box, the phrase "Say "Ok Google"" would only appear momentarily and then would switch to "Search". This caused the voice search never to start whenever I said "Ok Google".


I found out that the issue was caused by Keepass2Android Autofill service:
by disabling it in the phone's Settings|Accessibility
then the search box would always show "Say "OK Google"" again.
↧
Search

Edited Unassigned: Autofill service conflicts with Google app's voice search [599]

September 24, 2016, 3:45 am
$
0
0
I have Nexus 5x using Android N.

I had noticed that I whenever I switched to Google app home screen or the phone's home screen,
then in the search box, the phrase "Say "Ok Google"" would only appear momentarily and then would switch to "Search". This caused the voice search never to start whenever I said "Ok Google".


I found out that the issue was caused by Keepass2Android Autofill service:
by disabling it in the phone's Settings|Accessibility
then the search box would always show "Say "OK Google"" again.
↧
↧

Edited Unassigned: Autofill service conflicts with Google app's voice search [599]

September 24, 2016, 3:46 am
$
0
0
I have Nexus 5x using Android N.

I had noticed that I whenever I switched to Google app home screen or the phone's home screen,
then in the search box, the phrase "Say "Ok Google"" would only appear momentarily and then would switch to "Search". This caused the voice search never to start whenever I said "Ok Google".

I found out that the issue was caused by Keepass2Android Autofill service:
by disabling it in the phone's Settings|Accessibility
then the search box would always show "Say "OK Google"" again.
↧

Created Unassigned: Database name hidden on unlock screen when keyboard open, sometimes [600]

September 24, 2016, 6:38 am
$
0
0
On the database unlock screen, the database filename is shown, but only if the keyboard is not open. As kp2a has the cursor in the password field upon opening, that means I need to dismiss the keyboard to check the filename before clicking in the password field, each time.

Strangely, if I rotate to landscape and back to portrait, the display looks different, with the filename showing. Maybe you don't need to shrink the header when the keyboard opens in the first place.

↧

Edited Unassigned: Database name hidden on unlock screen when keyboard open, sometimes [600]

September 24, 2016, 6:42 am
$
0
0
On the database unlock screen, the database filename is shown, but only if the keyboard is not open. As kp2a has the cursor in the password field upon opening, that means I need to dismiss the keyboard to check the filename before clicking in the password field, each time.

Strangely, if I rotate to landscape and back to portrait, the display looks different, with the filename showing. Maybe you don't need to shrink the header when the keyboard opens in the first place.

Screenshots with keyboard closed, keyboard open, and after rotating lanscape/portrait.

↧
↧

Edited Unassigned: Database name hidden on unlock screen when keyboard open, sometimes [600]

September 24, 2016, 6:43 am
$
0
0
On the database unlock screen, the database filename is shown, but only if the keyboard is not open. As kp2a has the cursor in the password field upon opening, that means I need to dismiss the keyboard to check the filename before clicking in the password field, each time.

Strangely, if I rotate to landscape and back to portrait, the display looks different, with the filename showing. Maybe you don't need to shrink the header when the keyboard opens in the first place.

Screenshots with keyboard closed, keyboard open, and after rotating lanscape/portrait.

↧

Commented Unassigned: Error while connecting to webdav using TLSv1.2 only [595]

September 24, 2016, 8:49 am
$
0
0
I recently decided to switch my webdav service to TLSv1.2 only. Previously I was using TLSv1.0 TLSv1.1 and TLSv1.2. Owncloud webdav is hosting my Keepass2android files.

Since this change (and no other), now when I type in password to open my keepass file (the webdav password is remembered by keepass2android), I'm having the following error message:

> An error occured: Error: SecureChannelFailure (The authentication or decryption has failed.)

All other HTTPS services, also moved to TLSv1.2 are working perfectly, including the Owncloud which I use as webdav, from both Owncloud Android Client

My Android version is 6.0.
Comments: Tried reducing the server side attack surface by allowing just TLSv1.1, doesn't work either. TLSv1 is required by Keepass2Android.
↧

Commented Unassigned: Choosing key file from "System file picker" mangles stored location on restart [573]

September 24, 2016, 3:25 pm
$
0
0
I have a key file stored in my local storage or SD card.

When I use "System file picker" to find this key file, I can successfully use it with my master password to open my database.

But when I restart my phone, the remembered key file name goes from "ben.key" to some mangled form which does not work. Trying to use this to open my database gives an error message (see attached screenshot). From the text of the error message, it seems the app may have forgotten to ask for a required permission.

Using the file picker again lets me open the database but this is very annoying to need to do every single time I open my database.
Comments: This issue seems related to having moved my Keepass2Android installation to my SD card to save space. I moved it back to internal storage because it was causing the keyboard to be disable every time I restarted the phone. Now that it is back in internal storage, the key file is correctly remembered.
↧
Search

Created Unassigned: Option to export key [601]

September 25, 2016, 12:28 pm
$
0
0
Please and an option to export a key file that has been imported in to internal storage if the database is unlocked (for security).
↧
↧

Created Unassigned: Google drive permissions [602]

September 25, 2016, 1:35 pm
$
0
0
Please update the Google Drive permissions so Keepass2Android only has access to the files and folders it creates.
↧

Commented Unassigned: Google drive permissions [602]

September 26, 2016, 3:17 am
$
0
0
Please update the Google Drive permissions so Keepass2Android only has access to the files and folders it creates.
Comments: Although this sounds like a good idea, would it not cause problems when loading an existing database that was already in Google drive. My use case would be Keepass2Android and Keepass on Windows PC both using the same file on Google drive.
↧

Commented Unassigned: Google drive permissions [602]

September 26, 2016, 8:26 am
$
0
0
Please update the Google Drive permissions so Keepass2Android only has access to the files and folders it creates.
Comments: I guess this may cause a problem I wish Google would just use app folders like Dropbox.
↧

Created Unassigned: Please separate HTTPS and Webdav [603]

September 26, 2016, 11:29 am
$
0
0
Hi
I have my keepass database on my own HTTPS server. This is not a Webdav server, so I'd like Keepass2Android to _not_ show the username/password dialog (because the server does not ask for a password). I have to leave the dialog empty and just press OK, it works fine. Still, it's quite annoying and not what an user would expect.
↧
↧

Commented Unassigned: Cached database corrupted (sometimes) [483]

September 27, 2016, 6:38 am
$
0
0
Hi! Am I the only one having issues using the app when my phone is offline? Not always, just sometimes.

In such cases it is supposed to read the cached database, but after entering my password I got a message that says that the database is corrupted.

Any idea?

Thanks
Comments: As nobody answered my question, let me add some details: the app access my kdbx file via webdav (http://...) protocol on a Qnap TS-121 server.
↧

Created Unassigned: Suspicious Internet Connection [604]

September 27, 2016, 8:38 am
$
0
0
The Internet-savvy version of KeepPass2Android accesses https://xaapi.xamarin.com which is a) undocumented and b) a server based in Amazon's cloud.

There might be reasons related to the develpoment environment used, but IMO such "hidden" and unannounced connections are at least unlucky!
↧
Search

Created Unassigned: Fingerprint Unlock keeps getting disabled. [605]

September 29, 2016, 6:53 am
$
0
0
I'm having an issue that after enabling a Fingerprint unlock on a DB, after a while it gets disabled. I then have to enter the password manually and enabled fingerprint unlock again in the Database Settings.
Could this be caused by my Tasker profile which removes Pin lock when I connect to specific Wifi networks (using Secure Settings).
I'm not sure if that is the cause because I tested the profile multiple times and the Fingerprint didn't get lost and even when the Pin lock is removed, the fingerprints are still there (in Android Settings/Security)..

Is there a way for me to troubleshoot this? Anyway to get a log file?
↧

Commented Unassigned: sometimes remote db and cache are not synced [410]

October 1, 2016, 3:41 am
$
0
0
I am using keepass2andoid 0.9.8c with a remote db on Google Drive (gdrive://user@gmail.com/xxx.kdbx) (Using a passphrase and a composite key that is stored locally.)

Everything wors fine at first but after some weeks, a remotely modified database won't be synced anymore.
Keepass2Android always says "remote database and cache match" or something like that. (My german version says "_Remote-Datei und Cache stimmen überein_".) Selecting synchronize database inside an opened database yields the same message.

I can verify that the remote file is updated by checking the timestamp in the android google drive app.

At this point the only way to switch to the current state of the remote database is to drop the current database cache completely by closing the database, removing it from the recently opened DBs and add it again.

Comments: I am having the same problem. Synchronizing works correctly when I edit or add entries in the app. __But__, when I edit the file in Drive through another program (in my case, KeepassX), Keepass2Android no longer correctly synchronizes. It won't get the updated file from Drive (even if it says so), and it won't update the file on Drive anymore if an entry is edited/added in the app. The Synchronize database option in the overflow menu doesn't help either, as it incorrectly says that "No changes detected", even if the file __has__ indeed changed. A very annoying issue, I hope this gets solved in the near future.
↧
↧

Commented Unassigned: extra row for numbers on keyboard [324]

October 2, 2016, 9:22 am
$
0
0
add another row on top of the letters for direct access to the number keys
Comments: I was going to ask the same, but I gave my vote to this item! The best would be like Google's keyboard that is showing the extra row with numbers only when a "password field" is detected!
↧

Created Unassigned: Give a suggestion in the setting of encryption rounds [606]

October 3, 2016, 1:20 am
$
0
0
Hi,

Keepass2Android allows user to config the encryption grounds of their database. Although there is a tip gives the relationship between encryption grounds and security/speed . but it is still hard to tell that how should a normal range be.

I wonder if we can have a button in the setting activity that test how many grounds of encryption is acceptable on the phone (maybe count for 1 second?), just like the Keepass does.
↧

Commented Unassigned: Fingerprint Unlock keeps getting disabled. [605]

October 3, 2016, 3:43 am
$
0
0
I'm having an issue that after enabling a Fingerprint unlock on a DB, after a while it gets disabled. I then have to enter the password manually and enabled fingerprint unlock again in the Database Settings.
Could this be caused by my Tasker profile which removes Pin lock when I connect to specific Wifi networks (using Secure Settings).
I'm not sure if that is the cause because I tested the profile multiple times and the Fingerprint didn't get lost and even when the Pin lock is removed, the fingerprints are still there (in Android Settings/Security)..

Is there a way for me to troubleshoot this? Anyway to get a log file?
Comments: This is so true. Seeing this behaviour on Marshmallow 6.0.1.
↧
Viewing all 955 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>