Transient_invalidation_error in chrome://invalidations on Android. |
||||
Issue descriptionENVIRONMENT and STATS Chrome version: 53.0.2785.24 OS: Android REPRO STEPS 1. Sign in to Chrome. 2. In a new tab open chrome://invalidations ACTUAL RESULTS Observe that "TRANSIENT_INVALIDATION_ERROR" displayed at the top. EXPECTED RESULTS No errors are seen. ADDITIONAL INFO Even though Transient_invalidation_error is shown the actual invalidations are being received properly and are displayed in the invalidations log.
,
Jul 27 2016
,
Jul 29 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0cd818d507de24f20c5a23f69cc94b52d7ace708 commit 0cd818d507de24f20c5a23f69cc94b52d7ace708 Author: pnoland <pnoland@chromium.org> Date: Fri Jul 29 23:13:20 2016 [sync] Transient_invalidation_error in chrome://invalidations on Android. invalidation_service_android never updated its logger instance's state, since the state is always enabled. This meant the logger only ever reported the state as its initial value, which is transient_error. This change causes invalidation_service_android to update the state to enabled upon construction. R=pavely@chromium.org BUG= 630406 [sync] re-enable SyncTest#testRename Review-Url: https://codereview.chromium.org/2201503002 Cr-Commit-Position: refs/heads/master@{#408799} [modify] https://crrev.com/0cd818d507de24f20c5a23f69cc94b52d7ace708/components/invalidation/impl/invalidation_service_android.cc
,
Jul 29 2016
,
Aug 4 2016
Verified in 54.0.2817.0. Invalidations are working fine without any errors. |
||||
►
Sign in to add a comment |
||||
Comment 1 by jnaveen@chromium.org
, Jul 21 2016