react-native-dotenv VS expo-firebase-authentication

Best way to store API keys in RN? I need to store the google autocomplete API key somewhere but react-native-config and react-native-dotenv can be reverse-engineered. Any ideas? Thanks!

To consume env variables in js code you'd need https://www.npmjs.com/package/react-native-dotenv — basically, it will allow to reference single variable in the js code and at compile time it will pick up current value from the config

It's not possible to use react-native-dotenv in native code files like `build.gradle` or `Info.plist`: https://github.com/goatandsheep/react-native-dotenv/issues/190

Then install the 'react-native-dotenv' library in your project with the below commands using NPM or Yarn.

While you still developing your app use this package https://www.npmjs.com/package/react-native-dotenv

I know, not a direct answer to your question, but if you're looking for file-defined custom properties, the typical solution is to use https://github.com/goatandsheep/react-native-dotenv

⚙️ Handel environment variables with react-native-env

There are a few special libraries from npm that are used to make all this work and we cover them all in the video. Specifically we needed an AsyncStorage library and dotEnv, a library to manage local environment variable for the application

It's time to use the Firebase project configuration in the Expo app. To do so, first install the Firebase SDK by running expo install firebase. Additionally, install react-native-dotenv by running npm install react-native-dotenv, so that environment variables can be imported in the app via an .env file. Next, add the module:react-native-dotenv plugin to the default Expo babel.config.js file.

We will be making use of the handy npm library react-native-dotenv

Following that, create the /screens directory mkdir src/features/sign-in/screens and the "sign in" screen touch src/features/sign-in/screens/SignInScreen.js. The "sign in" screen re-uses the , extending it to optionally support a custom submit button text. Note that if any error occurs, it'll be rendered using the component (full source code), which simply uses the component from native-base.

To being with, create the /components directory by running mkdir -p src/components and the email and password form touch src/components/EmailAndPasswordForm.js. The full code for the component can be found in the Github repository, but I'll highlight some of the important bits here.

The goal of this series of blog posts, is to provide a simple example of how to setup Expo and Firebase with email and password based authentication. When done, this app will support sign up, sign in, sign out, email verification, and password reset. All the code for this series of blog posts is available on this Github repository. Let's jump right in.