Remote Config

Prerequisites

firebase-basics

Troubleshooting Execution

Handling npx 403 Forbidden Errors

npx -y firebase-tools@latest

1. Inform the user: "I am unable to fetch the latest Firebase tools via npx due to a registry error."
2. Fallback: Attempt to use the local

   firebase

   command directly if the user confirms it is installed globally (

   npm install -g firebase-tools

   ).

Handling Project Context Issues

1. Check login: Run

   npx -y firebase-tools@latest login:list

   .
2. Prompt for ID: If logged in but no project is active, ask the user: "Please provide your Firebase Project ID to proceed."
3. Use Flag: Append

   --project <PROJECT_ID>

   to every subsequent command.

SDK Setup

• Android: android_setup.md
• iOS: ios_setup.md

Best Practices and Template Management

Fetching Strategies

• Load new values for next startup: The most effective pattern is to activate previously fetched values immediately on startup and fetch new values in the background to be used next time. This minimizes user wait time.
• Real-time Updates: Use the SDK's real-time listener to update the app instantly without a refresh when server-side configuration changes.

Template Management via CLI

Template Management via CLI

• Get current template: Save the remote template to a local JSON file for auditing or modification.
  bash

  npx -y firebase-tools@latest remoteconfig:get -o remote_config.json

• Autonomous Editing & Discovery : Modify the local

  remote_config.json

  directly. Determine the correct signal (e.g., device.country or percent) and update the "conditions" array and "parameters" map accordingly.
• MANDATORY: User Review and Verification : STOP and ask the user to verify your changes before proceeding to deployment.
  • Action: Inform the user: "I have prepared the changes in remote_config.json. Please review the file for accuracy. Once you are satisfied, tell me to 'deploy' to make the changes live."
• Deployment Orchestration : To push changes, you must ensure the environment is configured for deployment.
  • Config Mapping: If a firebase.json file is missing, create one to map the local JSON to the Remote Config service:
  json

    { "remoteconfig": { "template": "remote_config.json" } }

  • Deploy: Execute the partial deployment command
    bash

    npx -y firebase-tools@latest deploy --only remoteconfig

• Verification: After deployment, verify the update by listing the version history.
  bash

  npx -y firebase-tools@latest remoteconfig:versions:list

• Set In-App Defaults: Define baseline values to ensure the app functions offline or before the first fetch.
• Fetch and Activate: Retrieve values from the Firebase backend and apply them to the local UI/Logic.
• Template Management: Use the Firebase CLI to version-control, get, and deploy your config JSON files.