React Native

npm install @rerune/react-native@1.9.0 i18next react-i18next

# Expo
npx expo install @react-native-async-storage/async-storage

# React Native CLI (on React Native 0.74 and 0.75, install @react-native-async-storage/async-storage@^2)
npm install @react-native-async-storage/async-storage
cd ios && pod install

Since SDK 1.9.0, your app installs AsyncStorage itself. In Expo, run npx expo install @react-native-async-storage/async-storage. With the React Native CLI, run npm install @react-native-async-storage/async-storage, adding @^2 on React Native 0.74 and 0.75 or with Kotlin older than 2.1.0, then cd ios && pod install. ReRune supports 1.23.1 and later 1.x, 2.1.2 and later 2.x, and 3.1.1 and later. Rebuild your development or release client; Expo Go needs no rebuild. Translation updates cannot install native modules.

Keep local translation resources for first-run offline behavior. Configure i18next with the languages and namespaces your application needs. OTA updates target the translation namespace. On Hermes, add @formatjs/intl-pluralrules and import its polyfill, with the data of every language your app or the dashboard publishes, first in your entry file. Without it, plurals show the wrong form, with or without ReRune.

Use the same nativeOptions shape shown in the React chapter, including your existing resources, fallback language, and interpolation settings. Replace native i18next initialization with one ReRune.setup call at module scope in its own module, for example src/i18n.ts, and export the client. React Native setup starts the AsyncStorage restore and the update check right away, so do not create the client in a useState initializer.

import { ReRune } from '@rerune/react-native'

export const client = ReRune.setup({
  otaPublishId: '<READ_ONLY_OTA_PUBLISH_ID>',
}, nativeOptions)

import { ReRuneProvider } from '@rerune/react-native'

<ReRuneProvider client={client} defaultNS="translation">
  <App />
</ReRuneProvider>

import { Text } from 'react-native'
import { useTranslation } from 'react-i18next'

export function App() {
  const { t } = useTranslation()
  return <Text>{t('headline')}</Text>
}

• Native i18next configuration

Keep the application language selection in your existing i18next flow. Use the SDK runtime locale information when offering dashboard-managed languages. ReRune downloads only the languages the app shows and their fallbacks. When your app sets supportedLngs, list your dashboard languages there too: a dashboard-only language outside it is not downloaded. A component that reads another language through getFixedT or the lng option needs i18n.loadLanguages first.

AsyncStorage can retain successfully fetched content across restarts. If a built-in store write fails, the SDK can still apply the update in session memory; that fallback does not survive a restart. Clearing application storage also removes cached data. Test a fresh offline installation separately from an offline restart after a successful persisted update.

• Preview drafts with OTA staging

The linked Expo example pins SDK 1.9.0 and demonstrates native startup, runtime languages, variants, and manual refresh. Use the package README for the version-specific API reference. Example font and artwork dependencies are not SDK requirements.

• React Native package reference
• Runnable Expo example