Dan Hill

Matt had me give this a shot. Didn't work for me, unfortunately.

I definitely can give it a shot. Is there any drawback to the `.retry()` approach? I'm only seeing the retry trigger a single time in practice, so it seems pretty...

Shouldn't the `.switchMap()` unsub from the first call to .read() when it sees the second, though?

``` Subscription s1 = whorlwind.read().subscribe(); s1.unsubscribe(); // how long of a wait here is safe? Subscription s2 = whorlwind.read().subscribe(); s2.unsubscribe(); ``` The time above is apparently less than the time...

Right. It's an unfortunate case where you're trying to save us from the platform bug, which is definitely great! This is just a bit of a sharp corner in the...

I think I've found an interesting point here: due to the platform bug, it's also possible for the lockscreen to steal whorlwind's callback to `onAuthenticationError`, which means that `readerScanning` never...

> :flag-ca: Haha, sorry! Is there a log statement to look for in logcat that you're aware of for when the lockscreen registers? I'm sifting through a log now, but...

Ah, I was actually just able to repro by turning the phone completely off and then running the app from Android Studio - so in that case the lockscreen would...

So I think my statements above about the lockscreen hijacking whorlwind's onAuthenticationError call are untrue. After debugging through more, it seems like this is happening: 1) Lockscreen is up and...

I've found a bit more, here. If you subscribe and unsubscribe from the `read()` stream enough, eventually we'll hit a case where `FingerprintAuthOnSubscribe` calls `cancellationSignal.cancel()`, but we **never** receive a...