[Remote Config] Real-time listener stops receiving updates, with no onError, when the stream starts during a persisted backoff
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Read ConfigRealtimeHttpClient.beginRealtimeHttpStream() and the retry path it calls when a persisted backoff is active. Confirm how the connection-running flag affects canMakeHttpStreamConnection(), then check the existing Remote Config real-time stream tests for coverage of that path. Done means the stream retries after backoff ends and the listener can receive updates.
Written by the indexing model from the issue text.
Description
[READ] Step 1: Are you in the right place?
Yes, this is a bug in firebase-config in this repository.
[REQUIRED] Step 2: Describe your environment
- Android Studio version: **Android Studio Quail 4 | 2026.1.4
- Firebase Component: Remote Config (real-time updates,
addOnConfigUpdateListener) - Component version: 23.1.0
[REQUIRED] Step 3: Describe the problem
The app stops receiving Remote Config updates for as long as the process lives. Once this happens, a registered ConfigUpdateListener never fires again: values changed in the console never reach the app, and onError is never called, so the app can't detect or recover from it. Only killing the process brings updates back.
On Android a process can stay alive for days, so apps that rely on real-time updates (rather than frequent fetch() calls) keep running on stale config for that whole time. In our app, users stayed on old values for days.
When it happens: two conditions, in this order.
- A stream connection fails while the app is in the foreground. This means no network, or the server answering 408, 429, 502, 503 or 504. The SDK then persists a backoff end time in SharedPreferences. The backoff is about 2 minutes after the first failure (randomized ±50%) and doubles with each consecutive failure, up to 256 minutes. It survives process restarts and is cleared only by the next successful (200) connection.
- Before that backoff ends, the SDK starts the stream again. It does this whenever the app calls
addOnConfigUpdateListener(for example on a cold start) or comes back to the foreground. Both go throughstartHttpConnection()→beginRealtimeHttpStream(), which hits the backoff early return described below and leaves the stream stuck.
Both are routine. For example, the user opens the app on a flaky connection, switches away, and comes back a minute later. From then on the app receives no updates until the process is killed.
Steps to reproduce:
- Register a
ConfigUpdateListenerwith the app in the foreground. - Make the real-time stream connection fail while the app is in the foreground. Keep the app in the foreground until the attempt fails.
- Restore network access, kill the app, and relaunch it while the backoff is still in effect. Register the listener again.
- After the backoff end time has passed, publish a Remote Config change.
Expected: when the backoff ends, the stream reconnects and the listener receives the update.
Actual: no connection is attempted after the backoff ends, the listener receives nothing, and onError is never called.
Relevant Code:
In ConfigRealtimeHttpClient.beginRealtimeHttpStream(), the method sets isHttpConnectionRunning up front. The early return for an active backoff never clears it, because only the finally block of the connection task clears it:
public void beginRealtimeHttpStream() {
if (!checkAndSetHttpConnectionFlagIfNotRunning()) { // sets isHttpConnectionRunning = true
return;
}
ConfigSharedPrefsClient.RealtimeBackoffMetadata backoffMetadata =
sharedPrefsClient.getRealtimeBackoffMetadata();
Date currentTime = new Date(clock.currentTimeMillis());
if (currentTime.before(backoffMetadata.getBackoffEndTime())) {
// No connection was opened, but isHttpConnectionRunning is still true here.
// The retry below goes through canMakeHttpStreamConnection(), which requires
// !isHttpConnectionRunning, so it is silently dropped and the stream stays stopped.
retryHttpConnectionWhenBackoffEnds();
return;
}
// ...
}
Suggested fix: release the flag before scheduling the retry, since no connection was opened on this path:
setIsHttpConnectionRunning(false);
retryHttpConnectionWhenBackoffEnds();
return;
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 733
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 72
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firebase/firebase-android-sdk
-
Crashlytics plugin writes build ID lists in directory listing order, so APKs can differ between machinesPossibly taken @mrober claimed this 11 days ago. Openapi: crashlytics
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
firebase/firebase-android-sdk#8789 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
api: auth
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
firebase/firebase-android-sdk#8505 · 1 comment ·
Maintainers usually reply within 1 day
-
api: firebaseai
Difficulty 4/5 3-5 days Newbie friendliness 15/100
firebase/firebase-android-sdk#8835 ·
Maintainers usually reply within 1 day
-
api: auth
Difficulty 4/5 3-5 days Newbie friendliness 25/100
firebase/firebase-android-sdk#8832 ·
Maintainers usually reply within 1 day
-
Firestore: NoSuchElementException in SQLiteIndexManager.encodeValues for a != query with a trailing orderBy when cache index auto-creation is enabledPossibly taken @dconeybe claimed this 5 days ago. Openapi: firestore
firebase/firebase-android-sdk#8831 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in firebase/firebase-android-sdk
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
linagora/twake-calendar-side-service#1578 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
moneymanagerex/android-money-manager-ex#3122 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
tchiotludo/akhq#3438 ·
Maintainers usually reply within 1 day