Closed Vstory closed 3 years ago
I have just tested and the timeout works well. What do you mean by :
the notification still prompts "locked"
"locked" is not an available message for the database notification. There is only "database opened" and the "lock" button when the timeout has not sent the close request.
"locked" is not an available message for the database notification. There is only "database opened" and the "lock" button when the timeout has not sent the close request.
What I mean is that after the database is automatically locked, the notification still shows that the database can be locked.
Is this a known feature?
No this is not normal, the notification should disappear with the lock. But what disturbs me the most is that I can't reproduce the problem. I hope this is not specific to Xiaomi.
No this is not normal, the notification should disappear with the lock. But what disturbs me the most is that I can't reproduce the problem. I hope this is not specific to Xiaomi.
I have allowed self-starting and set the battery optimization whitelist. Normally, it should not be restricted by the system. Don't kill my app!
No this is not normal, the notification should disappear with the lock. But what disturbs me the most is that I can't reproduce the problem. I hope this is not specific to Xiaomi.
Wait a minute, I will try to reproduce and get a logcat log.
Sorry, I tried a few times just now and it hasn’t recurred.
logcat.zip The problem reappeared.
I don't even know what I'm looking for in your logs if there's no crash. Can you tell me when you saw the problem because your log is a file over two whole days.
I don't even know what I'm looking for in your logs if there's no crash. Can you tell me when you saw the problem because your log is a file over two whole days.
It was the next day. At that time, I crawled the log, but it was inconvenient for feedback, so I kept it. This does not affect the use, mainly because the notification status is displayed incorrectly. It occasionally appears on my device.
I fixed a theoretical case where it could happen, I upload version 2.10.0 and you will tell me if you still have the problem.
I fixed a theoretical case where it could happen, I upload version 2.10.0 and you will tell me if you still have the problem.
OK. Wait for the push of the Google Play Store.
This problem should be fixed and has not been discovered recently. Thank you.
Thank you for your feedback! ;)
Describe the bug The database unlock status in the notification is incorrect.
To Reproduce Steps to reproduce the behavior:
KeePass Database
KeePassDX:
Android: