[alex-so-3]

Two cases where a Google Find Hub tracker looked as if Google had not answered:

• Quiet for more than a week. A fetch reads only the last seven days of Google's reports, so a tracker nobody had passed for longer came back with nothing, and a Google-only tracker had no position at all. When the week has no report, the newest older one is added: it is still where Google last saw the tracker.
• "Home" instead of coordinates. When the owner's own phone sees the tracker, Google answers a locate request with a named place ("Home") and no coordinates. Those reports were dropped, so a refresh that Google did answer looked unanswered. The newest named place is now kept (in memory; every fetch reads it again), and the map card adds it when it is newer than the position on the card: Last Updated: 2 hours ago · Google: Home, 5 minutes ago.

No schema change. One new string, in all locales.

Found on a DIY tag whose Google side looked dead: the service held a "Home" answer from that day and a week-old report from another phone, and the app showed neither.

Tested:

• New JVM tests in ReportSourcesTest and ExtraSourcesApiTest. I broke the choice of the newest older report on purpose and the test failed.
• testDebugUnitTest and add_strings.py --check pass.

Not tested yet:

• On a phone. I will update this once it has run on one.
• The instrumented suite. The card line has no instrumented test; the decision behind it is covered on the JVM.