
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
@nativescript/firebase-remote-config
Advanced tools
This plugin allows you to use the Firebase Remote Config API in your NativeScript app.
You need to set up your app for Firebase before you can enable Firebase Remote Config. To set up and initialize Firebase for your NativeScript app, follow the instructions on the documentation of the @nativescript/firebase-core plugin.
To add the Firebase Remote Config to your app, follow these steps:
@nativescript/firebase-remote-config plugin by running the following command in the root directory of your project.npm install @nativescript/firebase-remote-config
@nativescript/firebase-remote-config module. You should import this module once in your app, ideally in the main file (e.g. app.ts or main.ts).import '@nativescript/firebase-remote-config';
Default in-app values help ensure that your application code runs as expected in scenarios where the device has not yet retrieved the values from the remote server.
To create default in-app Remote Config parameters, follow the steps:
app.ts or main.ts)
.xml file with the parameter values to your app.
.xml file to the Remote Config object by calling the setDefaultsFromResource method.import { firebase } from '@nativescript/firebase-core';
firebase()
.remoteConfig()
.setDefaultsFromResource("remote_config_defaults")
.then(() => {
console.log('Default values set.');
});
import { firebase } from '@nativescript/firebase-core';
firebase()
.remoteConfig()
.setDefaults({
awesome_new_feature: 'disabled',
})
.then(() => {
console.log('Default values set.');
});
To create new server-side default values that override the in-app values, see Set parameter values in the Remote Config backend
Once you've created your parameters in the Remote Config backend, you can fetch them from the server and activate them in your app. You can first fetch the values from the server and then activate them, or you can combine the two tasks into a single flow with the fetchAndActivate method.
import { firebase } from '@nativescript/firebase-core';
firebase()
.remoteConfig()
.setDefaults({
awesome_new_feature: 'disabled',
})
.then(() => remoteConfig().fetchAndActivate())
.then((fetchedRemotely) => {
if (fetchedRemotely) {
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');
}
});
Although Remote Config is a data storage, it is not designed for frequent reads. By default, Firebase caches the parameters for 12 hours. By design, this prevents the values from being able to change frequently and potentially causes users confusion.
import { firebase } from '@nativescript/firebase-core';
// Fetch and cache for 5 minutes
await firebase().remoteConfig().fetch(300);
0.Note Be warned Firebase may start to reject your requests if values are requested too frequently.
minimumFetchIntervalMillis property of the RemoteConfigSettings object to the number of milliseconds to cache the values for. This can be done in the bootstrap file before the app starts:import { firebase } from '@nativescript/firebase-core';
remoteConfig().settings.minimumFetchIntervalMillis = 30000;
To read the fetched and activated parameters in your app, you can Read a single parameter or Read all parameters at once.
To read a single parameter value from the activated parameter values, call the getValue method on the Remote Config object. The getValue method returns a ConfigValue object, which you can use to get the value as a specific type (e.g. string, number, boolean, etc).
import { firebase } from '@nativescript/firebase-core';
const awesomeNewFeature = firebase().remoteConfig().getValue('awesome_new_feature');
// resolves value to string
if (awesomeNewFeature.asString() === 'enabled') {
enableAwesomeNewFeature();
}
// resolves value to number
// if it is not a number or source is 'static', the value will be 0
if (awesomeNewFeature.asNumber() === 5) {
enableAwesomeNewFeature();
}
// resolves value to boolean
// if value is any of the following: '1', 'true', 't', 'yes', 'y', 'on', it will resolve to true
// if source is 'static', value will be false
if (awesomeNewFeature.asBoolean() === true) {
enableAwesomeNewFeature();
}
To read all the parameters from the Remote Config object at once, call the getAll method. The getAll method returns an object with the parameter keys as the object keys and the ConfigValue objects as the object values.
import { firebase } from '@nativescript/firebase-core';
const parameters = firebase().remoteConfig().getAll();
Object.entries(parameters).forEach((item) => {
const [key, entry] = item;
console.log('Key: ', key);
console.log('Source: ', entry.getSource());
console.log('Value: ', entry.asString());
});
When a value is read, it contains source data about the parameter. If a value is read before it has been fetched & activated then the value will fall back to the default in-app value set. If you need to validate whether the value returned from the module was local or remote, call the getSource method on the ConfigValue object:
import { firebase } from '@nativescript/firebase-core';
const awesomeNewFeature: ConfigValue = firebase().remoteConfig().getValue('awesome_new_feature');
if (awesomeNewFeature.getSource() === 'remote') {
console.log('Parameter value was from the Firebase servers.');
} else if (awesomeNewFeature.getSource() === 'default') {
console.log('Parameter value was from a default value.');
} else {
console.log('Parameter value was from a locally cached value.');
}
import { firebase } from '@nativescript/firebase-core';
remoteConfigAndroid: com.google.firebase.remoteconfig.FirebaseRemoteConfig = firebase().remoteConfig().android;
A read-only property that returns the naive object for Android wrapped by the instance of the RemoteConfig class.
import { firebase } from '@nativescript/firebase-core';
remoteConfigIos: FIRRemoteConfig = firebase().remoteConfig().ios;
A read-only property that returns the naive object for iOS wrapped by the instance of the RemoteConfig class.
import { firebase } from '@nativescript/firebase-core';
remoteConfigApp: FirebaseApp = firebase().remoteConfig().app;
A read-only property that returns the FirebaseApp instance for the current app.
import { firebase } from '@nativescript/firebase-core';
remoteConfigFetchTimeMillis: number = firebase().remoteConfig().fetchTimeMillis;
A read-only property that returns the timestamp (milliseconds since epoch) of the last successful fetch, regardless of whether the fetch was activated or not.
import { firebase } from '@nativescript/firebase-core';
remoteConfigLastFetchStatus: 'success' | 'failure' | 'no_fetch_yet' | 'throttled' = firebase().remoteConfig().lastFetchStatus;
A read-only property that returns the status of the most recent fetch attempt.
import { firebase } from '@nativescript/firebase-core';
remoteConfigSettings: ConfigSettings = firebase().remoteConfig().settings;
// or
firebase().remoteConfig().settings = {
fetchTimeMillis: 43200000,
minimumFetchIntervalMillis: 30000,
};
Gets or sets the settings for this RemoteConfig instance.
import { firebase } from '@nativescript/firebase-core';
activated: boolean = await firebase().remoteConfig().activate();
Asynchronously activates the most recently fetched configs, so that the fetched key-value pairs take effect. For more information, see activate() on the Firebase website.
import { firebase } from '@nativescript/firebase-core';
await firebase().remoteConfig().ensureInitialized();
import { firebase } from '@nativescript/firebase-core';
await firebase().remoteConfig().fetch(expirationDurationSeconds);
Fetches parameter values from the Remote Config backend, adhering to the default or specified minimum fetch interval. For more information, see fetch() on the Firebase website.
| Parameter | Type | Description |
|---|---|---|
expirationDurationSeconds | number |
import { firebase } from '@nativescript/firebase-core';
activated: boolean = await firebase().remoteConfig().fetchAndActivate();
Asynchronously fetches and then activates the fetched configs. For more information, see fetchAndActivate() on the Firebase website.
import { firebase } from '@nativescript/firebase-core';
parameters: Record<string, ConfigValue> = firebase().remoteConfig().getAll();
Returns an object with all the parameters in the Remote Config.
import { firebase } from '@nativescript/firebase-core';
value: boolean = firebase().remoteConfig().getBoolean(key);
Returns the parameter value for the given key as a boolean.
| Parameter | Type | Description |
|---|---|---|
key | string | The key of the parameter to get. |
import { firebase } from '@nativescript/firebase-core';
value: number = firebase().remoteConfig().getNumber(key);
Returns the parameter value for the given key as a number.
| Parameter | Type | Description |
|---|---|---|
key | string | The key of the parameter to get. |
import { firebase } from '@nativescript/firebase-core';
value: string = firebase().remoteConfig().getString(key);
Returns the parameter value for the given key as a string.
| Parameter | Type | Description |
|---|---|---|
key | string | The key of the parameter to get. |
import { firebase } from '@nativescript/firebase-core';
value: ConfigValue = firebase().remoteConfig().getValue(key);
Returns the parameter value for the given key as a ConfigValue.
| Parameter | Type | Description |
|---|---|---|
key | string | The key of the parameter to get. |
import { firebase } from '@nativescript/firebase-core';
await firebase().remoteConfig().reset();
Deletes all activated, fetched and default configurations and resets all Firebase Remote Config settings.
import { firebase } from '@nativescript/firebase-core';
await firebase().remoteConfig().setDefaults(defaults);
Sets default configs from a ConfigDefaults object.
| Parameter | Type | Description |
|---|---|---|
defaults | ConfigDefaults | The default configs object to set. |
interface ConfigDefaults {
[key: string]: number | string | boolean;
}
import { firebase } from '@nativescript/firebase-core';
await firebase().remoteConfig().setDefaultsFromResource(resourceName);
Sets default configs using an XML resource.
| Parameter | Type | Description |
|---|---|---|
resourceName | string | The resource name of the XML resource in the package's res folder. |
This object is returned by the getValue() method and represents a parameter value for a given key. It provides several methods to get the value as a boolean, number or string.
configValue: ConfigValue = firebase().remoteConfig().getValue(key)
configValueAndroid: com.google.firebase.remoteconfig.FirebaseRemoteConfigValue = configValue.android;
Returns an instance of ConfigValue for Android.
configValue: ConfigValue = firebase().remoteConfig().getValue(key)
configValueIOS: FIRRemoteConfigValue = configValue.ios;
Returns an instance of ConfigValue for iOS.
configValue: ConfigValue = firebase().remoteConfig().getValue(key)
value: boolean = configValue.asBoolean();
Gets the parameter value as a boolean.
configValue: ConfigValue = firebase().remoteConfig().getValue(key)
value: number = configValue.asNumber();
Gets the parameter value as a number.
configValue: ConfigValue = firebase().remoteConfig().getValue(key)
value: string = configValue.asString();
Gets the parameter value as a string.
configValue: ConfigValue = firebase().remoteConfig().getValue(key)
source: 'default' | 'static' | 'remote' = configValue.getSource();
Gets the source of the parameter value.
Apache License Version 2.0
FAQs
NativeScript Firebase - Remote Config
The npm package @nativescript/firebase-remote-config receives a total of 239 weekly downloads. As such, @nativescript/firebase-remote-config popularity was classified as not popular.
We found that @nativescript/firebase-remote-config demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 19 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.