- #How to unlock norton password vault with fingerprint update
- #How to unlock norton password vault with fingerprint code
- #How to unlock norton password vault with fingerprint free
A quick search shows nothing for Samsung fingerprint in use here.
#How to unlock norton password vault with fingerprint code
It tends to lean this way, that if one app works and one doesn't then what's the difference? This one applies Google's code but not Samsung's as far as I noticed in my brief look at it. Sadly, 2016 is terribly close to that time when Samsung devices have an issue and developers just last year have been struggling with it. Developers have already thought about this last year anyway: Maybe additional research could show where it changes.Īdditional reference. An s7 edge from 2016 is quoted as working fine so in-between 20 devices could have a problem and there's no telling if Samsung improved it with all devices by/during 2016. The developers posted with the link in 2016.
#How to unlock norton password vault with fingerprint update
Is 2016 old enough, I don't know and don't have a 2016 model available to test and perhaps a newer update voided the issue anyway.įor additional reference the note 4 in the link was released in 2014 and had the problem. Its also not a theory as the link shows other developers have faced a problem there in the past. I also said my A7 (2017) model does not have this problem which is exactly what you're saying about your A8 (2018) model. At some point the compatibility has improved. Sorry, this is in reference to older Samsung devices specifically an older Samsung A5(2016) of which I said "This might fall under". It does not explain the "invalid key problem" message, or the fact that the problem is fixed by reinstalling the app, as others reported, or that it occurs on new devices. The theory that this specific problem is caused by config or older Samsung API implementation issues. But that's really up to them and what they desire the app to be like.Īll of this can be extrapolated from my previous post without having had to spell it out. There are many potential problem areas, not just what I wrote in my post and better reporting to the user will make various things clear that are not. I want it fixed or improved for you as I don't need it fixed since it works with no problem on my device.
On top of that, I've briefly examined their code before making the previous post and am on your side. Others have already pointed out various problems so I pointed out some more and its context is in addition to other posts. I know you're unhappy with how the app is performing and its in the back of my mind to submit a pull request and help out. Theory? I have cited developer references, a device without issue with the app, as well as stating that there could be additional problems, and I'm a app developer myself thank you very much =)
Samsung A8 2018, KeyPassDroid displays "invalid key problem" and does not react to the fingerprint sensor. Hope that helps someone understand a little better and not too technical besides the links It seems some work may be needed here to support devices that are failing where possible and to express it better to the user if they can't be used or if they don't have the device set up correctly, etc.Īndroid P however has some changes for those who would like to know and they would also be good to implement here which should further improve user interaction in the future. In fact if it actually has a problem there than Google's API is really bad that it can't work on their own devices. The fact that it fails with a Nexus 6P however, what's up with that one -) I get 0 search results of people with Nexus devices having a problem with it. They may have a different range of support added as its quite clear cut with how Google code works and so its not like it should fail unless Google's API fails to return an "OK" to the app - though lots of stuff needed to do one just this one thing as is usual with Google sometimes.Ĭertainly, I would think there could be failure in other ways as well here such as with the encryption object that is needed which could potentially have its own problems on some devices and so on. If you have it work with one app and not with this one then I think the other apps are not using or not just using Google's fingerprint API which I see is used here. There's also supposedly another issue where a device config may not supply the needed flag if you will resulting in it failing:
Knowing where its failing at would figure that out however. So, I really think its a user error or that. I have a Samsung A7 sitting here and it works fine. This might fall under the following linked issue where older Samsung devices return false with Google's finger print API FingerprintManager and needed Samsung's version (thank you Samsung, thank you Google)
#How to unlock norton password vault with fingerprint free
Now that I have a little more free time, I see that there's an Samsung A5 with a problem.
0 kommentar(er)
