react-native-config VS Detox

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!

React Native Config bring you the ability, for example, to have different environments which will make it easier to work with different API endpoints and test your application.

have you looked at react-native-config?

It’s recommended to use react-native-config and react-native-dot-env to place your secure key, endpoint.

I put all my API keys and global config elements into here. I have a single file with an object which is indexed with they key PROD STAGE or DEV, which is pulled from a CURRENT_ENV.tsx file. I write to this file using a simple bash script and a make command. Alternatives to this are things like react-native-config but those packages don't obfuscate anything either so I could never justify their extra complexity.

Honestly, security wise it doesn't matter too much where you store it in the app. It'll be accessible one way or another. Common practice is that variables like this would be stored in a config/environment file. See: https://github.com/luggit/react-native-config

There are a few ways to use environment variables in React Native, but I used react-native-config. Setup is very simple:

Nope. Not even on 0.71 yet https://github.com/wix/Detox/issues/3884

This article offers an overview of React Native testing, but there’s so much more to learn! I encourage you to explore other testing techniques and tools, like Snapshot Testing, Detox, and React Native Testing Library. Choose the ones that work best for your project, and keep learning!

I used Detox to test React Native apps. At that time, Detox was so "cool", saving both the time and effort of the dev team and the tester team. However, later on, I saw the complexity, as well as the "difficulty" with new team members, and that's when Maestro came to me as a savior. I know Maestro through an article on dev.to, but my team's "noob" is true 😂 (but my teammates don't believe it).

End-to-end testing is completely different on React Native, however. None of the Selenium-based E2E testing tools will work; neither will newer tools like Cypress or Playwright. You may have expected this - these are all DOM-based, and there’s no DOM in React Native. So instead developers will have to learn Detox or Appium.

Detox is a testing and automation tool for React Native and React web applications. It can be used to automate the process of testing an iOS app by simulating user interactions and then verifying that the app functions as expected.

I haven't used it yet, but it seems detox is a fine e2e testing tool for react native. something like cypress in the web. I think it's a little hard to configure, but in the end, it's really helpful.

The standard is React Native Testing Library for unit and integration tests, and Detox for E2E tests.

We also improved our React Native support by adding the possibility to generate a Detox config for Expo applications.

Copy & paste the content of the equivalent file from the detox example app for RN, into it. Don't forget to change the package name to your project's package name.

Detox is great for React Native: https://wix.github.io/Detox/