Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

Gmail calendar synch issue

  • /e/ version: 0.17-20210621120947
  • Device model(s): FP3
  • Device rooted: ?

Summary

Calendars from google accounts stopped synchronizing after update to /e/ OS 0.17 (again).

The problem

Steps to reproduce

Trying to refresh the calendars synchronization.

What is the current behavior?

The calendars do not synch anymore.

What is the expected correct behavior?

The calendars should synch downwards and upwards automatically.

Technical informations

Relevant logs (adb logcat)

--- BEGIN DEBUG INFO --- SYNCHRONIZATION INFO Account name: XXX@gmail.com

HTTP REQUEST: Request{method=PROPFIND, url=https://apidata.googleusercontent.com/caldav/v2/XXX%40gmail.com/events/, tags={}}

HTTP RESPONSE: Response{protocol=h2, code=401, message=, url=https://apidata.googleusercontent.com/caldav/v2/XXX%40gmail.com/events/}

EXCEPTION: foundation.e.dav4jvm.exception.UnauthorizedException: HTTP 401 at foundation.e.dav4jvm.DavResource.checkStatus(DavResource.kt:411) at foundation.e.dav4jvm.DavResource.checkStatus(DavResource.kt:397) at foundation.e.dav4jvm.DavResource.processMultiStatus(DavResource.kt:491) at foundation.e.dav4jvm.DavResource.propfind(DavResource.kt:384) at foundation.e.accountmanager.DavService.refreshCollections(DavService.kt:329) at foundation.e.accountmanager.DavService.access$refreshCollections(DavService.kt:39) at foundation.e.accountmanager.DavServiceonStartCommand$inlinedletlambda$1.invoke(DavService.kt:76) at foundation.e.accountmanager.DavServiceonStartCommand$inlinedletlambda$1.invoke(DavService.kt:39) at kotlin.concurrent.ThreadsKtthreadthread$1.run(Thread.kt:30)

SOFTWARE INFORMATION

  • foundation.e.accountmanager 2.6.3-ose (328)
  • com.android.providers.contacts 10 (29)
  • com.android.providers.calendar 10 (29)
  • foundation.e.tasks 1.2.3-48-g3636f1f (7100)
  • com.android.contacts 1.7.31 (10731)
  • foundation.e.calendar 1.0.21 (23)

CONNECTIVITY (at the moment)

  • [ Transports: CELLULAR Capabilities: SUPL&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&NOT_CONGESTED&NOT_SUSPENDED LinkUpBandwidth>=15000Kbps LinkDnBandwidth>=30000Kbps Specifier: <1>]
  • [ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED LinkUpBandwidth>=1048576Kbps LinkDnBandwidth>=1048576Kbps SignalStrength: -77]

[...]

Relevant screenshots

2021-06-29_08.31.50

Solutions

Workaround

?

Possible fixes

?

Edited by Corentin Wicht