Call AppIndexingReporter on AsyncTask

Call AppIndexingReporter on AsyncTask

It doesn't need to run on main thread, and lazy Firebase
initialization makes disk read.

BUG=

[wychen, 2017-04-10 23:17:59]

Description was changed from

==========
Call AppIndexingReporter on AsyncTask. It doesn't need to run on main thread,
and lazy Firebase initialization makes disk read.

BUG=
==========

to

==========
Call AppIndexingReporter on AsyncTask

It doesn't need to run on main thread, and lazy Firebase
initialization makes disk read.

BUG=
==========

[wychen, 2017-04-10 23:22:23]

wychen@chromium.org changed reviewers:
+ wychen@chromium.org

[wychen, 2017-04-10 23:22:24]

https://codereview.chromium.org/2806383004/diff/20001/chrome/android/java/src...
File chrome/android/java/src/org/chromium/chrome/browser/AppIndexingUtil.java
(right):

https://codereview.chromium.org/2806383004/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/AppIndexingUtil.java:46:
AsyncTask.execute(new Runnable() {
Probably makes sense to move AsyncTask to downstream, since upstream caller
doesn't "know" the details of the downstream implementation details.

[dproctor, 2017-04-10 23:23:16]

https://codereview.chromium.org/2806383004/diff/20001/chrome/android/java/src...
File chrome/android/java/src/org/chromium/chrome/browser/AppIndexingUtil.java
(right):

https://codereview.chromium.org/2806383004/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/AppIndexingUtil.java:46:
AsyncTask.execute(new Runnable() {
On 2017/04/10 23:22:23, wychen wrote:
> Probably makes sense to move AsyncTask to downstream, since upstream caller
> doesn't "know" the details of the downstream implementation details.

Sure, that makes sense.