[Android Apps and Games] mike.j:
Thanks for your commitment! And one more bug left...

Wow, these past few days haven't been the finest moment of Lockdown, to say the least. The loop that was in the yesterday-version was particularly annoying, along with the fact that OFF didn't deactivate the app. Makes me think that maybe you starting a beta program (like, officially through the app store, for the brave and daring) wouldn't be a bad idea...don't mean to come across as harsh, just a thought..

With that said, kudos for the dedication that must have gone in to sorting the issues out! I'm sure you've had quite a busy weekend. I just installed the latest version available like minutes ago from the Play Store and almost everything that broke is fixed. Can't say I had any doubts, I've been checking the app store on an hourly basis since the loop version yesterday, convinced that it would get fixed before today is over. And of course you delivered!

Like I said, kudos! The occasional bug I can live with, indifferent developers - not so much. I never doubted you, and I'm so satisfied with shelling out a couple of bucks for premium even though ilovexda. ;)

Now, enough with the off topic ramblings, and over to the one tiny, hard to spot, bug that got introduced with the first of the plenty recent updates. Ehrrm. :P

Fingerprint scanning. It doesn't work when there's another scan waiting for feedback underneath. And it did before. Nexus 6p here with Google imprint. (WOW, do i looove the support for Google imprint, by the way?! Yes, yes I do.)

Let me break it down point by point, to make it super clear.

I have Lastpass set up to ask for authentication every time I open it. And Lockdown Pro to lock Lastpass whenever I'm off my home wifi. And what happens is as follows:

1. Open Lastpass.

2. Get fake cover screen.

* This step is "invisible" since it happens behind the fake cover, but this is where lastpass pops up the "Authenticate with your fingerprint" screen, behind/underneath Lockdowns fake cover (obviously).

3. I touch the scanner, and I feel the vibration confirming that my finger print was read.

4. Nothing happens. Fake cover remains. I try touching the scanner again, and again, but nothing. No vibration. There's simply nothing there expecting a reading from the scanner. It would seem.

5. Long press the fake cover and do the pattern swipe.

6. I'm now logged in/authenticated in Lastpass. And I've never seen the finger print request. Which is weird, right? 'cause Lastpass should always require my fingerprint before opening my vault...

So, obviously...Lockdown draws over the finger print inquiry of Lastpass. But the latter has priority to get access to the imprint input.

I'm not sure how Imprint works on a technical development level, but I would venture a guess that Lockdown expects to have an open line to the scanner, and Lastpass telling imprint that we're done for now? Or, does Lastpass just break the current imprint listen for Lockdown by overriding it? I dunno why I'm even speculating, I'm sure you got the mechanics like two paragraphs ago.

So yeah, that's the one issue still remaining that I could find from how

I

use Lockdown. In no way a dealbreaker for me, temporarily. As far as I'm concerned, take the week off from developing and get to it sort of soon'ish, or thereabouts. I'm sure you could use a break right now. :)