whitelabel_env.sh

SPLASH_SCREEN_BG_COLOR="#f8f8f8" #background color used when generating the splash screen
SKU="<Appstore Connect SKU>" #sku used when generating a new app within appstore connect 
WHITE_LABEL_NAME="Cool App QA" #The name of the app as appears under the icon
BASE_URL="https://api.com" #url used for making api requests
UNIQUE_WHITELABEL_ID="<unique_whitelabel_id>" #a unique id differentiating each app
BUNDLE_IDENTIFIER="com.organization.unique.bundle.id" #unique: identifies the app within the appstore/googleplay
DEEPLINK_SCHEME="<deeplink_scheme>" #the deeplink URL prefix ex: myappscheme://
FIREBASE_DEEPLINK_URL="<firebase_deeplink_url>" #for deeplinking
ANDROID_GEO_API_KEY="<Google Maps Android API Key>" #used for google maps api calls on Android
IOS_GEO_API_KEY="<Google Maps IOS API Key>" #google maps api calls on iOS
MIXPANEL_PROJECT_TOKEN="<mixpanel_project_token>" #sending analytic events
BUGSNAG_NOTIFIER_API_KEY="<bugsnag_api_key>" #reporting crashes to bugsnag
CodePushDeploymentKey="<android_codepush_api_key>" #iOS code push deployment key
CodePushDeploymentKey_iOS="<ios_codepush_api_key>" #Android code push deployment key

Hello @cohen72, I found your post about white labeling with react native, your post is excellent. 👏👏

I had a question, because in your .env file you have some identical variables? For example: SKU and SPLASH_SCREEN_BG_COLOR?

@CesarBarros Hey Carlos :) Thanks for your feedback! Actually that's a Typo! Thanks for finding that! I fixed it :) BTW, I have since updated my approach to store all the white label directories, including the .env files in a separate repository, and use the CI to checkout the appropriate folder from that separate repo. In this way, I remove the main repo's vulnerability for storing all of these keys.

Hello @cohen72, I found your post about white labeling with react native, your post is excellent. 👏👏
I had a question, because in your .env file you have some identical variables? For example: SKU and SPLASH_SCREEN_BG_COLOR?

@CesarBarros Hey Carlos :) Thanks for your feedback! Actually that's a Typo! Thanks for finding that! I fixed it :) BTW, I have since updated my approach to store all the white label directories, including the .env files in a separate repository, and use the CI to checkout the appropriate folder from that separate repo. In this way, I remove the main repo's vulnerability for storing all of these keys.

@cohen72 Perfect I understand, this new approach of yours is very good. 😉

I'm using this approach with the .keystore and the match action to create/manage certificates and provisions in another git repository.

If you want to know more about how to do it, there is information at https://medium.com/reactbrasil/como-configurar-o-fastlane-com-seu-aplicativo-react-native-6a11f5781759 (it is in Portuguese, but it is possible to translate )