> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/integration/implementation-steps/react-native.md).

# React Native

## Step 1: Prerequisites

### Android Requirements

All apps must have a Firebase project and matching credentials to capture subscriptions and send notifications. Follow the link below to create a Firebase project for your app and add the credentials to our platform.

Before you can integrate the SDK with your app the following requirements must be met:

* Android device or emulator running API 24+ (Android 7.0) with Google Play Store Services installed.
* An app that uses [<mark style="color:blue;">Jetpack (AndroidX)</mark>](https://developer.android.com/jetpack/androidx/migrate)
* Firebase Sender ID and Server API Key or Service Account. If you do not already have these follow [<mark style="color:blue;">our documentation</mark>](/integration/implementation-steps/android/firebase-app-setup.md) to generate them.
* SDK Key: Obtained from the Pushly Platform in the `Domain Settings` page under the `Details` > `Domain Information` section.

{% hint style="warning" %}
**React Native SDK 1.7+**

The bundled native Android SDK depends on `androidx.core` 1.17 and carries Kotlin 2.2 metadata, so a consuming project must build with a matching toolchain:

* Kotlin 2.2 or newer
* Android Gradle Plugin 8.9.1 or newer
* `compileSdk` 36
* `minSdk` 24
* JDK 17–21
  {% endhint %}

#### React Native architecture

The SDK works with either React Native architecture. It ships both a TurboModule and a legacy bridge implementation, and selects between them using your project's `newArchEnabled` Gradle property.

### iOS Requirements

In order to begin subscribing users to notifications you must have either a P8 Key (recommended) or a P12 Certificate; Either of these can be generated via the Apple Developers portal.

* An [<mark style="color:blue;">Apple Developer Account</mark>](https://developer.apple.com/account/) that has Admin privileges
* Your application's App Bundle ID (e.g., `com.pushly.example`)
* An iOS application or XCode project with the Push Notifications capability added

In addition to the above the following requirements must be met:

* An iOS 15.1+ device (iPhone, iPad, or iPod Touch) to develop and test on, or a simulator that meets the requirements in [<mark style="color:blue;">Testing on a simulator</mark>](/integration/implementation-steps/apple-ios/sdk-swift-obj-c.md#testing-on-a-simulator).
* A Mac OS device with XCode 15.1+ installed.
* An iOS P12 Push Certificate or P8 Key. If you do not already have these follow [<mark style="color:blue;">our documentation</mark>](/integration/implementation-steps/apple-ios/p8-key-or-p12-cert-setup.md) to generate them.
* SDK Key: Obtained from the Pushly Platform in the `Domain Settings` page under the `Details` > `Domain Information` section.

{% hint style="info" %}
The iOS deployment target and XCode version are set by React Native, not by the Pushly SDK, so a newer React Native version may raise both above the floors listed here.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.pushly.com/integration/implementation-steps/react-native.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.