| commit | f936d8290c2f4b81a6718099253a222c0b8c15fe | [log] [tgz] |
|---|---|---|
| author | Vinit Nayak <peanutbutter@google.com> | Wed Dec 01 11:42:40 2021 -0800 |
| committer | Vinit Nayak <peanutbutter@google.com> | Wed Dec 01 11:42:40 2021 -0800 |
| tree | a3f6ea05399bb46aabd490510daad9ac7c971dc4 | |
| parent | d4377890cf008b0693dae52c52c8e1751464cdfa [diff] |
Initialize content resolver in ctor * In ag/16337218 we moved the initialization of the context into the ctor instead of init(), but not the content resolver. * When we add a callback for OverviewProxyService in the ctor, it might call the onConnectionChanged() before NavBarHelper#init() is called, which would lead to use of a null content resolver in updateAssistantAvailability() Bug: 208261632 Change-Id: I306cdf27c7870ad72e80ef401367bb0d6dc32f68