![\"\"](\"brand/logo.png\"){kind=logo}
\n\n \n
\n Config variables for React Native apps, supporting iOS, Android, macOS and Windows.\n
\n\nExpose config variables to your JavaScript code — bring some\n[12 factor](http://12factor.net/config) love to your mobile apps!\n\n> [!TIP]\n> **Help keep this library maintained.** If `react-native-config` is useful to you or your\n> company, please consider\n> [sponsoring it on Open Collective](https://opencollective.com/react-native-config).\n> Contributions go toward the maintenance work that keeps it working across new React Native\n> releases. See [Sponsors](#sponsors) for the tiers and what sponsorship pays for.\n\n## Basic Usage\n\nCreate a new file `.env` in the root of your React Native app:\n\n```\nAPI_URL=https://myapi.com\nGOOGLE_MAPS_API_KEY=abcdefgh\n```\n\nThen access variables defined there from your app:\n\n```js\nimport Config from \"react-native-config\";\n\nConfig.API_URL; // 'https://myapi.com'\nConfig.GOOGLE_MAPS_API_KEY; // 'abcdefgh'\n```\n\nKeep in mind this module doesn't obfuscate or encrypt secrets for packaging, so **do not store sensitive keys in `.env`**. It's [basically impossible to prevent users from reverse engineering mobile app secrets](https://rammic.github.io/2015/07/28/hiding-secrets-in-android-apps/), so design your app (and APIs) with that in mind.\n\n## Setup\n\n> ⚠️ Note (Android): react-native-config v1.6.0+ requires React Native 0.74 or higher. \n> If you use an older RN version, see Troubleshooting below.\n\nInstall the package:\n\n```\n$ yarn add react-native-config\n```\n\nLink the library:\n\nOn React Native 0.60 and above there is no link step — the library is\n[autolinked](https://reactnative.dev/blog/2019/07/03/version-60#native-modules-are-now-autolinked).\nRebuild the app so the native side is picked up. On iOS / macOS, install the pod first:\n\n```\n(cd ios; pod install)\n```\n\n> [!WARNING]\n> Do not link this library manually on React Native 0.60 or above, and do not disable its\n> autolinking in `react-native.config.js`. Autolinking is what registers the native module and,\n> on the New Architecture, generates its TurboModule bindings — adding\n> `include ':react-native-config'` to `android/settings.gradle` instead does neither, and the\n> module then resolves to `null` at runtime. See\n> [TypeError: Cannot read property 'getConfig' of null](#typeerror-cannot-read-property-getconfig-of-null).\n\n(Note: For Windows, this module supports autolinking when used with `react-native-windows@0.63`\nor later. For earlier versions you need to manually link the module.)\n\n