React Native Firebase Remote Config Not Working on Vega

Vega Open Beta Bug Reports
1

:backhand_index_pointing_right: Bug Description

1. Summary

I am trying to integrate Firebase Remote Config in a Vega React Native app by provided guide:

However, I’m facing issues while implementing Remote Config.

App Name:
App Link on Amazon Appstore

Bug Severity
Select one that applies

  • Impacts operation of app
  • Blocks current development
  • Improvement suggestion
  • Issue with documentation (If selected, please share the doc link and describe the issue)
  • Other

2. Steps to Reproduce

    1. Create a new Vega React Native application.

    2. Add Firebase configuration const firebaseConfig = {

      apiKey: '',

      authDomain: ‘webconfig-.firebaseapp.com’,

      projectId: ‘webconfig-’,

      storageBucket: ‘webconfig-.firebasestorage.app’,

      messagingSenderId: ‘’,

      appId: ‘1::web:’,

      measurementId: ‘G-’,

      }; and initialize Firebase in App.tsx.

    3. Install @react-native-firebase/app and @react-native-firebase/remote-config.

    4. Implement Remote Config using either:

    5. Call remoteConfig().setDefaults() and attempt to fetch values using fetch() or fetchAndActivate().

    6. Build and deploy the app on Vega / Fire TV device.

    7. Launch the app and observe logs.3. Observed Behavior

Explain what actually happened, noting any discrepancies or malfunctions.

Only the initialized status is printed.

Remote Config values are not returned / printed.

3. Expected Behavior

Describe what you expected the SDK to do under normal operation.

App should print:

Firebase initialized status

Remote Config value

4.a Possible Root Cause & Temporary Workaround

Fill out anything you have tried. If you don’t know, N/A is acceptable

Possible Root Cause:
Firebase Remote Config APIs (fetch() / fetchAndActivate()) may not be fully supported or properly wired in the Vega React Native environment. While initialization succeeds, Remote Config values are not returned, and calling fetchAndActivate() results in an application crash.

Temporary Workaround:
Currently no workaround identified. Tried both Vega community documentation and RNFirebase official implementation. Also attempted setting default values and fetching configs separately, but Remote Config values are still not accessible.

5. Environment

Please fill out the fields related to your bug below:

  • SDK Version: 0.22.5600
  • App State: [Foreground/Background]
  • OS Information
    sh(com.amazon.dev.shell):/$ cat /etc/os-release
    NAME=“OS”
    OE_VERSION=“4.0.0”
    OS_MAJOR_VERSION=“1”
    OS_MINOR_VERSION=“1”
    RELEASE_ID=“14”
    OS_VERSION=“1.1”
    BRANCH_CODE=“TV Ship day60”
    BUILD_DESC=“OS 1.1 (TV Ship day60/4454)”
    BUILD_FINGERPRINT=“4.0.198430.0(3072cab629675a74)/4454N:user-external/release-keys”
    BUILD_VARIANT=“user-external”
    BUILD_TAGS=“release-keys”
    BUILD_DATE=“Sat Dec 20 04:05:59 UTC 2025”
    BUILD_TIMESTAMP=“1766203559”
    VERSION_NUMBER=“1401010445450”

6. Example Code Snippet / Screenshots / Screengrabs

Include any relevant code or component setup in React Native that can help reproduce the bug.

import React, { useEffect } from 'react';
import remoteConfig from '@react-native-firebase/remote-config';

function App() {
  useEffect(() => {
    remoteConfig()
      .setDefaults({
        awesome_new_feature: 'disabled',
      })
      .then(() => {
        console.log('Default values set.');
      });
  }, []);
}

import remoteConfig from ‘@react-native-firebase/remote-config’;

remoteConfig()
.setDefaults({
awesome_new_feature: ‘disabled’,
})
.then(() => remoteConfig().fetchAndActivate())
.then(fetchedRemotely => {
if (fetche@react-native-firebaseRemotely) {
console.log(‘Configs were retrieved from the backend and activated.’);
} else {
console.log(
‘No configs were fetched from the backend, and the local configs were already activated’,
);
}
});

:backhand_index_pointing_right: Playback Issues

If this is a playback issue, please provide your content URL, any pre-conditions (like geo-location), and let us know if it’s x86 or arm7.


NA

Please share the following details in addition:_

  • Player SDK: [Bitmovin, Shaka, ...]
  • Player SDK Version: [e.g. 1.23]
    • Audio Codecs: [AAC, ...]
    • Video Codecs: [h.264, mp4]
    • Manifest Types: [m3u8, dash, etc ..]

Q: If applicable, please provide your media/content url
If this is created dynamically, tokenized, etc please provide a way for us to access it

NA

Q: Are there any special headers required to reproduce the issue you are facing?

NA

Additionally please provide the following if possible
Provide Screenshots / Screengrabs / Logs. Please include as much information as you can that will help debug.

<!-- Answer here if applicable -->
3

Hi @Pankaj_kumar ,

Welcome to the Amazon developer community.

As mentioned in the community guide, for any issues specific to using React Native Firebaseyou can reach out to the Invertase team directly at oss@invertase.io.
You can also find detailed documentation at https://rnfirebase.io/

Thank you,
Rohit

4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.