Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

keepass2android Issue Tracker Rss Description

older | 1 | .... | 45 | 46 | (Page 47)

    0 0

    The input form is blocked by the keyboard. It would be nice if you could scroll away to see the form.

    Other than that, loving the app so far!

    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: Can you please switch to the beta channel (https://play.google.com/apps/testing/keepass2android.keepass2android) and see if the issue is fixed there?

    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: I'm on the beta channel for some weeks now and this error did not happen to me for some time now. Had this before though.

    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: I originally raised this issue, but also haven't encountered it in a long while. However, when I raised it (Sep 29, 2016), I was on a Samsung Galaxy S5 Duos. I moved to a Oneplus 3 in November 2016. So it could be a phone specific or Android specific version issue as I haven't noticed it on my OP3. I'm currently on v 1.01-g Since other people are still encountering the issue, maybe we should still keep it open.

    0 0

    When an entry is opened, the app shows two notification icons - one for the database, another for the entry available through the KP2A keyboard.

    Having two icons is excessive and inelegant. I believe the new app users can be put off by that complexity. An open entry implies an open database. The database icon should be hidden if the keyboard icon is shown.

    0 0

    The app stopped getting the updated database from Google Drive. There was no indication of the problem except that the entries added on desktop machines would not appear in the app.

    Reinstalling the app fixed the problem.

    Actually, the app was showing an error "Looks like account was not properly initialized!" before the reinstall. That message is now gone. But that message started appearing long time ago (perhaps a few months ago), and I haven't had any issues with synchronization until yesterday.

    Too bad I cannot reproduce the issue anymore. Perhaps future version of the app should make synchronization errors more prominent so that users would report issue while still experiencing it.

    0 0

    Hi,
    I've tried to enable a Fingerprint unlock to my database however I'm still asked for the password and next to it there is a red exclamation mark which shows "Error initializing Fingerpring Unloc Java.Lang.RuntimeException: Attempt to invoke virtual method....". I'm running 6.0.1 on note 4. Anyone hit similar issue?

    Regards,
    Peter

    Ful error:
    ```
    Error initializing Fingerprint Unlock: Java.Lang.RuntimeException: Attempt to invoke virtual method 'byte[] java.lang.String.getBytes()' on a null object reference
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0xae9ad7c8 + 0x00024> in <filename unknown>:0
    at Android.Runtime.JNIEnv.CallStaticObjectMethod (IntPtr jclass, IntPtr jmethod, Android.Runtime.JValue* parms) <0xae5ae720 + 0x000c3> in <filename unknown>:0
    at Android.Util.Base64.Decode (System.String str, Base64Flags flags) <0x9b6b5d88 + 0x001cf> in <filename unknown>:0
    at keepass2android.FingerprintDecryption..ctor (keepass2android.FingerprintModule fingerprint, System.String keyId, Android.Content.Context context, System.String prefKey) <0x9b6b4498 + 0x00087> in <filename unknown>:0
    at keepass2android.PasswordActivity.InitFingerprintUnlock () <0x9b6b3c38 + 0x0018f> in <filename unknown>:0
    --- End of managed exception stack trace ---
    java.lang.NullPointerException: Attempt to invoke virtual method 'byte[] java.lang.String.getBytes()' on a null object reference
    at android.util.Base64.decode(Base64.java:118)
    at md5f0702f468598c68ce18586502249fb40.PasswordActivity.n_onResume(Native Method)
    at md5f0702f468598c68ce18586502249fb40.PasswordActivity.onResume(PasswordActivity.java:102)
    at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1286)
    at android.app.Activity.performResume(Activity.java:6987)
    at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4144)
    at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4246)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1838)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:158)
    at android.app.ActivityThread.main(ActivityThread.java:7225)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
    ```
    Comments: I have the same issue on my LG G6, Android 7.0. On my previous LG G5 it was working fine.

    0 0

    When you have multiple entries for the one website or entity, and use Tags to differentiate, it is impossible to work out which search result is appropriate.

    Especially when sharing a website location from a browser to Keepass2Android, which makes entry selection really convenient. But when all the search results look the same, it becomes a much longer process to select the correct entry (because you have to guess, then return to the browser, and if it's the wrong entry, you have to go through the whole process again).

    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: I was able to solve this issue for me. The reason in my case was that Keepass2Android expected the database file on Dropbox to be lowercase (e.g. 'database.kdbx') while my desktop client (KeeWeb) stored it upercase (e.g. 'Database.kdbx'). Like this the fingerprint unlock sometimes worked, sometimes not, depending on which client did write the database last. Since I corrected this, fingerprint unlock works ALWAYS and I'm a very happy person again! :-D

    0 0


    0 0


older | 1 | .... | 45 | 46 | (Page 47)