| commit | b224622c29679e83ac4b42bc7ae6553456391629 | [log] [tgz] |
|---|---|---|
| author | Kevin Chyn <kchyn@google.com> | Thu Jul 11 15:01:26 2019 -0700 |
| committer | Kevin Chyn <kchyn@google.com> | Thu Jul 11 15:03:21 2019 -0700 |
| tree | 9212571cbfe86097fb69bf048b4405b4753cc414 | |
| parent | c3ee236a950f0e4ea3b78b2247b1ad97828f4de9 [diff] |
Do task stack work on handler to ensure in-order execution
The rest of the ClientMonitor work is done on a handler to guarantee
in-order execution. e.g. setting to null when auth completes, updating
mCurrentClient when new client is requested, etc. Put this work on the
same handler.
Fixes: 137237140
Test: BiometricPromptDemo, go home while authenticating multiple times;
no crash observed
Change-Id: I43126ce13fb88d751571d0d52fe594c0293f794c