react-native-code-push VS react-native-config

Your testing team is using AppCenter.

Appcenter will allow you to build your app for iOS and install on your device without submitting to the App Store. https://appcenter.ms/

I used expo-updates with a CI script to push updates. CodePush is also a good alternative.

We've been using app center for build distribution (https://appcenter.ms/)

But, https://appcenter.ms/ and others like it are already available with generous free tiers and a lot more features (which you don't have to use, but can grow into), not to mention GitHub actions as others have noted. Does this advantages over existing, standard solutions?

There are lots of choices. Google android device testing. Offhand https://appcenter.ms comes to mind.

you don t need a mac, use microsofts app center to build it. https://appcenter.ms

I've heard good things about App Center from Microsoft https://appcenter.ms/

Don’t muck with automating simulators, it’s a PITA: we used https://aws.amazon.com/device-farm/ and it was ok. This was pretty ok: https://bitrise.io As much as I hate Microsoft, https://appcenter.ms was workable, but required the most calories and was slow.

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: