Can't Repro
Status Update
No update yet.
Comments
pa...@gmail.com
Same problem, but not only with simulator.
pa...@gmail.com
Suffering same issue. java.io.IOException: grpc failed after calling geocoder.getFromLocation()
It happens on all emulator APIs I've tried (API levels tested were 23, 24, 25 using x86_64 Google APIs images and API 26 using x86 Google APIs ) Real devices seem to work fine. Definitely a more recent issue since my app is many years in development and this was not always a problem. My app falls back to usehttps://maps.googleapis.com/maps/api/geocode/json?latlng=. .. but this is a quota limited API and slow.
It happens on all emulator APIs I've tried (API levels tested were 23, 24, 25 using x86_64 Google APIs images and API 26 using x86 Google APIs ) Real devices seem to work fine. Definitely a more recent issue since my app is many years in development and this was not always a problem. My app falls back to use
mu...@google.com
This is working for me on all of my emulator APIs that were previously failing a couple of days ago (21 through 25). Just curious - does anyone know how the fix was delivered? I didn't manually update my Android software.
Description
When a "Reply to" assist has been triggered for a read email in the important category it causes it to appear incorrectly as a search result when using a query such as "label:inbox label:unread is:important". Querying the API further you can confirm that the message does not have the unread label yet is still returned as a result. This happens irregardless of which client used (e.g. node, swift etc...)
What steps will reproduce the problem?
1. Receive an email, label it important, read it, and wait for the "Reply to" assist to appear on the thread
2. In the web UI search for "label:inbox label:unread is:important" and see no results returned
3. Query the API using
4. Fetch the message using
What is the expected output? The message should not be returned as it does not match the query and the search results should be the same as those returned by the web interface. There's no additional information in the email data as to why it's been returned
What do you see instead? The message always returned for the query. No obvious way to filter it out other than fetching all messages and filtering manually. No additional information the message about why it's been returned.
Please provide any additional information below.
It's also possible to reproduce the issue other variations on the api endpoint, such as...
* q="label:inbox is:unread is:important"
* q="label:inbox -is:unread is:important"
* labelIds=["INBOX", "UNREAD", "IMPORTANT"]
* labelIds=["INBOX", "UNREAD", "IMPORTANT"]&q="label:inbox is:unread is:important"