---
title: Platforms
description: >-
  Supported platforms and minimum OS/JDK versions, with the firebase-js-sdk
  fallback for web/macOS/Windows and its limitations for Auth, Database,
  Firestore and Storage.
previous: /ios-spm
next: /faqs-and-tips
---
> ## Documentation Index
> Fetch the complete documentation index at: https://rnfirebase.io/llms.txt
> Use this file to discover all available pages before exploring further.

## Prerequisites

- `@react-native-firebase/app` installed. For Android and iOS native SDKs, complete [Getting Started](/) (config files, Expo plugins, or React Native CLI native setup) before relying on platform behavior described here.
- For web / macOS / Windows / other JavaScript-only targets ("Other" platforms below), you still install the same `@react-native-firebase/*` packages; the JS fallback runs automatically when no native module is present. Call `initializeApp` with a Firebase web config on those targets (see [Getting Started — Other / Web](/#other--web)).

## Status

By default React Native Firebase supports multiple platforms using the native Firebase SDK for the specific platform.

### Tooling and SDK pins

Confirm these before install or upgrade:

{/* prettier-ignore */}
| Requirement | Version |
| --- | --- |
| React Native | New Architecture enabled. `@react-native-firebase/app` declares the peer range `>=0.60.0-0` (not a tested floor). Tested on `0.88.0-rc.3` (Expo `58.0.0`) |
| Expo (when using Expo) | `@react-native-firebase/app` declares the optional peer range `>=47.0.0` (not a tested floor). Tested on Expo `58.0.0` (React Native `0.88.0-rc.3`) |
| Xcode (iOS builds) | `>= 26.2` |
| Firebase Apple SDK | `13.1.1` (default pin) |
| Firebase Android SDK | `35.0.2` (default pin) |
| JDK (Android builds) | `>= 17` |
| Kotlin Gradle plugin (Android builds) | `>= 2.4.0` |

From v26, every React Native Firebase package with a native bridge requires New Architecture. firebase-ios-sdk `12.12.0` and newer require Xcode `26.2` or newer; v27 pins firebase-ios-sdk `13.1.1` and `firebase-android-sdk` `35.0.2`.

### OS minimums

| Platform | Minimum Version       |
| -------- | --------------------- |
| Android  | 7.0 (API 24 / Nougat) |
| iOS      | 15.0                  |
| macOS    | 11.0                  |

To compile your application for Android, you need a minimum JDK (Java Development Kit) version of `>= 17` and a Kotlin Gradle plugin of `>= 2.4.0` (Firebase Android BoM 35 / `firebase-auth` 25 ships Kotlin **2.4.0** metadata). For ecosystem workarounds (unsupported older Kotlin, AsyncStorage KSP, Google Sign-In), see [Migrating to v27 § Ecosystem compatibility tips](/migrating-to-v27#ecosystem-compatibility-tips).

However, for platforms that we don't provide a Native Module for, React Native Firebase instead implements a fallback Firebase JS SDK implementation to support
these 'Other' platforms, e.g.;

- Web
- macOS
- Windows
- any other RN based environment without a React Native Firebase native module

Below is a table outlining which Firebase modules are supported on each platform in React Native Firebase:

| Firebase Service          | Android | iOS | Other |
| ------------------------- | :-----: | :-: | :---: |
| ai                        |   ✅    | ✅  |  ✅   |
| analytics                 |   ✅    | ✅  |  ✅   |
| app                       |   ✅    | ✅  |  ✅   |
| app-check                 |   ⚠️    | ⚠️  |  ⚠️   |
| app-distribution          |   ✅    | ✅  |  ❌   |
| auth                      |   ✅    | ✅  |  ⚠️   |
| crashlytics               |   ✅    | ✅  |  ❌   |
| database                  |   ✅    | ✅  |  ✅   |
| firestore                 |   ✅    | ✅  |  ⚠️   |
| functions                 |   ✅    | ✅  |  ✅   |
| in-app-messaging          |   ✅    | ✅  |  ⚠️   |
| installations             |   ✅    | ✅  |  ❌   |
| messaging                 |   ✅    | ✅  |  ❌   |
| perf                      |   ✅    | ✅  |  ❌   |
| phone-number-verification |   ✅    | ❌  |  ❌   |
| remote-config             |   ✅    | ✅  |  ✅   |
| storage                   |   ✅    | ✅  |  ⚠️   |
| `vertexai` (deprecated)   |   ✅    | ✅  |  ✅   |

- ✅ (supported)
- ⚠️ (partial support, including no-op stubs that resolve without effect) - see notes below
- ❌ (not supported)

`vertexai` is a deprecated JavaScript-only package; use `ai` instead (see [VertexAI](/vertexai/usage)).

## Other Platforms

Whenever the React Native Firebase SDK is running on platforms other than Android
or iOS, the internal implementation uses a fallback platform which is implemented
in JavaScript, using the [Firebase JavaScript Modular SDK](https://firebase.google.com/docs/reference/js).

No implementation changes are required to use the React Native Firebase SDK on
other platforms (with the exception of Async Storage detailed below), as the
JavaScript implementation is automatically used when a native platform is not
available. This allows you to use the same API across all platforms, regardless
of the underlying implementation.

There are however some minor limitations or differences in behavior compared
to the native platforms. Where a particular method is not supported, an error
will be thrown with a code of `unsupported` to indicate the method is not
available on the current platform.

Further details of Firebase service specific limitations are summarized below.

### Async Storage

Auth and Analytics on 'Other' platforms require an Async Storage implementation
to enable persistence. React Native Firebase provides an API to set this
implementation.

Install a storage package appropriate for your target (this example uses
`@react-native-async-storage/async-storage`; substitute your platform's
equivalent if needed):

`npm install --save @react-native-async-storage/async-storage` or
`yarn add @react-native-async-storage/async-storage`.

Call `setReactNativeAsyncStorage` before `initializeApp` during app bootstrap on
Other platforms:

```js
// codeblock-ignore: requires the @react-native-async-storage/async-storage package
import AsyncStorage from '@react-native-async-storage/async-storage';
import { initializeApp, setReactNativeAsyncStorage } from '@react-native-firebase/app';

async function bootstrapFirebase() {
  setReactNativeAsyncStorage(AsyncStorage);

  return initializeApp({
    apiKey: 'api-key',
    authDomain: 'project-id.firebaseapp.com',
    databaseURL: 'https://project-id.firebaseio.com',
    messagingSenderId: 'sender-id',
    projectId: 'project-id',
    storageBucket: 'project-id.appspot.com',
    appId: 'app-id',
  });
}
```

`initializeApp` rejects unless `apiKey`, `appId`, `databaseURL`, `messagingSenderId`, `projectId` and `storageBucket` are all strings, even when you do not use Realtime Database or Cloud Storage. See [Required options](/app/usage#required-options).

In `@react-native-async-storage/async-storage` major version 3 (as of 3.1.1), the default export is a proxy to the legacy version 2 storage and exists mainly as a migration path. The version 3 form is `createAsyncStorage(name)`, a named export that returns a storage instance bound to a database name, for example `setReactNativeAsyncStorage(createAsyncStorage('firebase'))`. That instance also has `getItem`, `setItem`, and `removeItem`. It opens its own database, so data already stored through the default export is not read from it.

You can pass any object that implements `getItem`, `setItem`, and `removeItem`
(the `ReactNativeAsyncStorage` interface) instead of either of those, for example a store backed by
your platform's own storage API.

If you do not provide an Async Storage implementation, we use an in memory implementation
which will result in resetting the data every time your app is restarted, in the case of
Firebase Auth this means your users have to sign in again and for Firebase Analytics the app will generate a new instance id and look like a new installation every time.

### Analytics

The other platform implementation of Analytics does not capture automatic metrics like screen view, you must call `logEvent` and other logging based methods to send your events to Firebase.

- [Screen Tracking Guide](/analytics/screen-tracking)

### App Check

App Check for other platforms only supports the `CustomProvider` provider. Prerequisites: `@react-native-firebase/app` and `@react-native-firebase/app-check` installed, and a default Firebase app already initialized (native config on Android/iOS, or `initializeApp` on Other platforms).

- [Implement server support to get tokens](https://firebase.google.com/docs/app-check/custom-provider)
- Create a custom provider in your app:

```js
import { getApp } from '@react-native-firebase/app';
import { CustomProvider, initializeAppCheck } from '@react-native-firebase/app-check';

const myCustomProvider = new CustomProvider({
  getToken: async () => {
    const tokenFromServer = 'some-token-from-server';
    // Token lifetime in milliseconds (one hour here); use the value your server returns.
    const lifetimeMillisFromServer = 60 * 60 * 1000;
    return {
      token: tokenFromServer,
      expireTimeMillis: Date.now() + lifetimeMillisFromServer,
    };
  },
});

await initializeAppCheck(getApp(), {
  provider: myCustomProvider,
});
```

### Authentication

Multi-factor authentication is not supported on other platforms.

Phone authentication methods are unsupported, specifically:

- `signInWithProvider`
- `signInWithPhoneNumber`
- `verifyPhoneNumberForMultiFactor`
- `confirmationResultConfirm`
- `verifyPhoneNumber`
- `reauthenticateWithProvider`

### Database

Offline persistence is not supported on other platforms.

Unsupported methods:

- `keepSynced` - for offline persistence

### Firestore

For performance reasons and to reduce the size of the JavaScript bundle, the Other platform implementation in
React Native Firebase uses the JavaScript [lite](https://firebase.google.com/docs/reference/js/firestore_lite) SDK,
which does not support methods related to offline & persistence.

Specifically, the following methods are not supported:

- `loadBundle`
- `clearPersistence` - for offline persistence
- `disableNetwork` - for offline persistence
- `enableNetwork` - for offline persistence
- `namedQuery`
- `onSnapshot` (for both `CollectionReference` & `DocumentReference`)
- `GetOptions.source`

### In-App Messaging

The Other platform implementation is a no-op stub. No in-app messages are displayed, and these methods resolve without effect:

- `setMessagesDisplaySuppressed`
- `setAutomaticDataCollectionEnabled`
- `triggerEvent`

### Storage

No-op methods:

- `setMaxDownloadRetryTime` (does not throw, but has no effect)

Unsupported methods:

- `writeToFile`
- `putFile`

---

## Known Issues

Known issues will be documented here and updated when they are confirmed.

- No known Other-platform issues are recorded on this page.
