bug 1492475 introduced a large amount of changes, but getting an Android build done locally took too much time to understand why Services.search wasn't resolved properly on Android. Does it need a clobber? Probably not, but time needs to be spent here to resolve this. However, this can continue without blocking other work.

We obviously won't merge cedar into m-c when the Search Service doesn't work on Android.

Florian, I re-requested review, because I changed direction substantially... the approach I've taken in the new patch is to fix up the Android Search Service shim. I explained things further in the commit message.

n-i, Florian, because I'm not sure whether the Phabricator flagging actually works.

(In reply to Mike de Boer [:mikedeboer] from comment #5)

n-i, Florian, because I'm not sure whether the Phabricator flagging actually works.

I have no idea what "the Phabricator flagging" means in this context, so I guess that means it didn't do what you wanted.