question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error when communicating with Google API(20): Timing out service connection

See original GitHub issue

Describe the bug

Opening the CWA for the first time today resulted in display of error message Fehler bei Kommunikation mit Google API(20), Error when communicating with Google API(20). Every opening of the app shows this error until Google API(39508) error kicks in (too many calls to API).

Today would have been the first time to have 14/14 active days. Now it stays at 13/14 days.

Sorry I cannot provide more details right now. Unfortunately I had USB debugging off and after switching it on, only the Google API(39508) error was captured in the log. Also, it is a massive hindrance to documentation not being able to take screenshots. I didn’t have another smartphone or a computer nearby when the error happened. Users of CWA on iOS apparently can take screenshots without hindrance. Friends on iPhones share screenshots of CWA with me all the time. Frustrating.

Expected behaviour

The app opens without any errors.

Steps to reproduce the issue

  1. Install the app on 16 June 2020 via Google Play Store, keep it updated, version is 1.0.4 before any error in CWA appears
  2. Use app with bluetooth and location on for some time every day; see days active incremented every day
  3. On 25 June 2020 see the Google API(10) error appearing for the first time; error does not appear again that days and days active are incremented when opening the app again
  4. See Google API(10) error appearing and disappearing on other days after that (I don’t have an exact log which days); days active are still incremented every day
  5. On 30 June 2020 see Google API(20) error appearing when opening CWA for the first time. Appears again every time the app is opened / put into foreground until no more calls to Google API possible (Google API(39508) error).

Technical details

Device

  • App Version: 1.0.4
  • Android Version: 6.0.1 (stock Android of device, not rooted)
  • Device Model and Manufacturer: Samsung S5 (SM-G900F)
  • Latest OS Update: can’t determine date, Android menu says all available updates installed
    • Kernel: 3.4.0-14131106 from 06 Aug 2018
    • Build number: MMB29M.G900FXXU1CRH1
  • Latest Update of CWA: update to 1.0.4
  • Installation Date of CWA: 16 June 2020
  • Date/Time of the error: 30 June 2020 about 9:00 local time Germany
  • Google Play Services version: 20.21.17 (040308-316502805)
  • Google Mobile Services (GMS) version:
    • com.google.android.gms [202117018] [20.21.17 (040308-316502805)] [Container]
    • com.google.android.gms.nearby_en [v202304013]

Additional context

This error happened for me after several days of seeing Fehler bei Kommunikation mit Google API(10) (Error when communicating with Google API(10)) when starting the app, as described in #771. Today, only the Google API(20) error appeared. The Google API(10) error so far seemed to “resolve itself” on my device, not reaching Google API(39508) error (too many calls to API); days active was incremented in those cases after the error was not displayed anymore. Google API(20) in contrast reappeared until no more calls to the API were possible. Days active was not incremented today.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:12 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
aurisnoctiscommented, Jul 27, 2020

Haven’t encountered this error recently. It seems CWA version 1.1.1 either avoids the Google API errors or the notifications, so I close this issue.

1reaction
jakobmoellersapcommented, Jul 2, 2020

Thanks for the detailed info. I will update once we investigated more closely and can give more input

Read more comments on GitHub >

github_iconTop Results From Across the Web

google maps - Connection Timeout - Get Request
It had worked with no issues for weeks, until yesterday, when I started getting a "Connection Timeout" error when using the API script....
Read more >
How to Fix the ERR_CONNECTION_TIMED_OUT Error - Kinsta
Simply put, it's an indication that the system is unavailable and the time given for one to connect has elapsed, and now the...
Read more >
CommonStatusCodes | Google Play services
The connection timed-out while attempting to re-connect. This failure indicates a connection to Google Play services was successfully ...
Read more >
Errors | Cloud APIs - Google Cloud
Client does not have sufficient permission. This can happen because the OAuth token does not have the right scopes, the client doesn't have...
Read more >
can't connect to google api it seems. | Linode Questions
That;s from the error log: > 2014/07/10 19:21:44 [error] 15072#0: *293 upstream timed out (110: Connection timed ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found