Modified variables are not updated after rebuilding #591

mickael-h · 2021-06-27T09:40:54Z

I keep changing variable values in the .env file, but recompiling the app doesn't change anything (at least on iOS)
I tried cleaning every cache I could think of, but the config values are still the same as the first build.
Could you give instructions in order to clean the .env cache?

VinitSarvade · 2021-07-16T09:50:16Z

@mickael-h Faced the same issue, fixed it by clearing the xcodederiveddata in your system.

hke-ghtest2 · 2022-10-18T07:33:31Z

Faced the same issue, every time need to manually remove node_modules/react-native-config/ios/ReactNativeConfig/GeneratedDotEnv.m.

Any updates on the handling?

pvroosendaal · 2022-11-04T13:18:16Z

Just removing the GeneratedDotEnv.m file didn't help me, that caused a compile error, because the import then fails in ReactNativeConfig.m, line 2. Running "Clean Build Folder" in Xcode works for me. This ensures the '[CP-User] Config codegen' build phase script in the Pods project is run again and the content of GeneratedDotEnv.m is regenerated.

hke-ghtest2 · 2022-11-08T03:00:07Z

@pvroosendaal , thanks for that update.
Yes Running "Clean Build Folder" in Xcode also works for me .
I think this is the better way for refreshing the cached content.

billnbell · 2022-11-13T02:53:40Z

how about another solution ?

billnbell · 2022-11-13T03:05:53Z

#700

Stas-Buzunko · 2022-12-09T03:32:43Z

running Running "Clean Build Folder" in Xcode does work.
But it's ridiculous we have to Clean build folder each time (we pass commit hash on build so env changes on each deployment) + ENVFILE path is ignored and we have to copy env file we need to .env. This library has ~250 opened issues, no idea how it's still the most popular lib for handling env variables...

i think it's time to switch to another library as we have wasted too much time on this one. Going to try react-native-dotenv, i don't think it could be worse than this one 🤣

luancurti · 2023-01-11T16:50:06Z

Fixed in 1.4.12

robsonos · 2023-01-12T03:40:34Z

Just tested here and it still does not update environment variables after rebuilding the code

alessioemireni · 2023-01-12T17:12:39Z

Same here. We need to reopen the issue.
The error occurs the second time. Example:
ENVFILE=.env.production yarn ios --> OK
ENVFILE=.env yarn ios --> KO
Then I retry but no success. Seems that the script works only the first time of app lunch.

rivaros · 2023-01-20T08:35:30Z

@luancurti We are verry sorry, but it does not work with 1.4.12. :) Pls reopen the issue.

dks333 · 2023-01-28T22:46:34Z

same, not working with 1.4.6

marcoj · 2023-02-03T10:38:27Z

Same in 1.5.0

TwistedMinda · 2023-02-06T16:27:21Z

Same in 1.4.5

billnbell · 2023-02-06T21:31:49Z

I just delete Pods and rerun yarn ios and it seems to always work for me.

pod deintegrate && pod install

TwistedMinda · 2023-02-14T09:43:22Z

I just delete Pods and rerun yarn ios and it seems to always work for me.

pod deintegrate && pod install

Perfect dude, thank you! This is the quickest! Not even a yarn start --reset-cache is needed
But of course, a yarn ios to rebuild with the new Pods is required

PS: You don't need pod deintegrate either

lclarkg18 · 2023-02-16T16:14:39Z

Same issue, pod install is not fixing it consistently though.

chdzma · 2023-02-21T11:46:50Z

Same with the last version, ios is cached all the time

billnbell · 2023-02-22T05:02:13Z

what canw e do to fix this?

nghiaklabs · 2023-03-08T08:53:17Z

Fixed in 1.4.12

It's not working

gCardinal · 2023-03-08T22:09:25Z

~~Adding my voice to this issue. At least on iOS, this isn't currently working.~~

Edit: I was wrong, it is working. Make sure the path to your .env file is an absolute path, not a relative one. I also need to clean the project's build with XCode, but otherwise, flawless.

engineerStuardo · 2023-03-11T00:37:46Z

hey @gCardinal what do you mean by Make sure the path to your .env file is an absolute path?? What should I do exactly?

billnbell · 2023-03-11T01:16:48Z

Everyone: This module is pretty simple. It generates a file and puts it in Pods. It does that when you yarn install - and only if it is not already there. So you have 2 choices. 1. Delete Pods - then rerun pod install or 2. pod deintegrate and then pod install

Got it?

engineerStuardo · 2023-03-11T11:55:26Z

@billnbell the problem is only on iOS that if I make a change on my .env file it doesn't read that change and keep the first one. I need to delete node_modules and until then reads the new one. Sorry I'm a beginner on this.

gCardinal · 2023-03-11T14:21:48Z

hey @gCardinal what do you mean by Make sure the path to your .env file is an absolute path?? What should I do exactly?

I mean instead of pointing to files like so ../../.env, I had to use the absolute path /Users/my-user/dev/project-name/.env.

I also did not need to delete my pods when changing a value - I do however need to clean the project in XCode. I am also not using the environment variable way to point to different files. I had to do it this way, so in the end I have something like this in my Podfile:

CURRENT_DIRECTORY = Dir.pwd()
PROJECT_ROOT = File.expand_path("#{CURRENT_DIRECTORY}/../../../")
ENV_FILES = {
  'Debug' => "#{PROJECT_ROOT}/.env",
  'Debug-Staging' => "#{PROJECT_ROOT}/.env.stg",
  'Debug-Prod' => "#{PROJECT_ROOT}/.env.prd",
  'Release' => "#{PROJECT_ROOT}/.env.dev",
  'Release-Staging' => "#{PROJECT_ROOT}/.env.stg",
  'Release-Prod' => "#{PROJECT_ROOT}/.env.prd",
}

# Then, in my post install hook:

  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      if target.name == 'react-native-config'
        config.build_settings['ENVFILE'] = ENV_FILES[config.name]
      end
    end
  end

This was what finally worked for me, but as I said, when I change values, I need to clean the project. No other way around it that I could find.

engineerStuardo · 2023-03-11T14:59:24Z

Thank you so much @gCardinal 🥇

jackkrone · 2023-04-10T15:53:17Z

@mickael-h Faced the same issue, fixed it by clearing the xcodederiveddata in your system.

This works for me. To be more specific, I added the following script to my package.json, which I run every time I change the contents of my .env file:

"deleteDerivedData": "rm -rf ${HOME}/Library/Developer/Xcode/DerivedData/*"

I am using different schemes in my project which means I have a .env.prod, .env.develop, and .env.qa file, the contents of which are copied into the main .env file when running the associated scheme. I always delete derived data before switching the scheme I'm running locally.

arundevkv · 2023-05-03T07:03:36Z

@jackkrone that worked for me. Thanks

toorandroidmaster · 2023-06-10T06:56:05Z

Faced the same issue, every time need to manually remove node_modules/react-native-config/ios/ReactNativeConfig/GeneratedDotEnv.m.

Any updates on the handling?

i fixed this issue using this
#698 (comment)

Irfanwani · 2023-07-11T17:19:07Z

Same issue with iOS still persists. for me deleting the pods and reinstalling them worked but it takes a lot of time for me for just to rewrite the env variables.

billnbell · 2023-07-11T18:19:27Z

Yeah to fix this correctly we need to add to the pipeline an env variable check or something "RESET_CONFIG=1" and then when building delete the file and re-generates. I am sure this is not a high priority - but the author of this package should see if there is a way to make this easier to regenerate the generated files.

developerdanx · 2023-07-15T14:43:52Z

This is still an issue. Seriously we don't have a good solution yet?

billnbell · 2023-07-15T16:52:01Z

I think they take PRs :)

nathantew14 · 2023-07-17T14:27:47Z

I tried pretty much everything suggested here and it still doesn’t work...

bodiavaleur · 2023-07-21T09:05:30Z

Got it fixed by generating GeneratedDotEnv.m on every build

Inside Edit scheme... -> Build -> Pre-actions

cp "${PROJECT_DIR}/../.env.production" "${PROJECT_DIR}/../.env"
"${SRCROOT}/../../../node_modules/react-native-config/ios/ReactNativeConfig/BuildXCConfig.rb" "${SRCROOT}/../.env" "${SRCROOT}/tmp.xcconfig"
"${SOURCE_ROOT}/../../../node_modules/react-native-config/ios/ReactNativeConfig/BuildDotenvConfig.rb" "${SOURCE_ROOT}/../.env" "${SOURCE_ROOT}/../../../node_modules/react-native-config/ios/ReactNativeConfig/"
^ Add this line and change relative path to your node_modules

nathantew14 · 2023-08-11T13:40:17Z

i gave up and started using expo. it just... works! never turning back.

Biplovkumar · 2023-09-07T10:43:57Z

I added "clear": "rm -f node_modules/react-native-config/ios/ReactNativeConfig/GeneratedDotEnv.m", in Package.json scripts. it is working fine. but is is a temporary solution.
I am using 1.5.1 and still facing same issue. Please resolve.

joaquinvaz · 2023-10-02T17:43:26Z

I'm having this issue, any solution? only running "Clean Build Folder" in Xcode does work

nathantew14 · 2023-10-05T03:29:11Z

I'm having this issue, any solution? only running "Clean Build Folder" in Xcode does work

Just use expo @Biplovkumar @joaquinvaz

henaharon · 2023-11-28T15:22:58Z

I have renamed .env.development
to
.env.integration
Works like a charm!

rolfen · 2024-01-17T19:37:27Z

I found the solution. I format my disk and reinstall the OS and the variable updates. Works every time.

PS: Found a trick on another github thread:

Manually edit the file importing react-native-dotenv by either adding an empty line or whitespace will work.

zetachang/react-native-dotenv#24 (comment)

arelstone · 2024-01-22T12:58:57Z

I found the solution. I format my disk and reinstall the OS and the variable updates. Works every time.

It works 100% of the times.. Thanks for the solution 👏 🎆

brunovollmer · 2024-02-08T10:28:53Z

Anything speaking against doing it like this:

rm -rf "${SRCROOT}/../node_modules/react-native-config/ios/ReactNativeConfig/GeneratedDotEnv.m"
cp "${PROJECT_DIR}/../.env.development" "${PROJECT_DIR}/../.env"  
"${SRCROOT}/../node_modules/react-native-config/ios/ReactNativeConfig/BuildXCConfig.rb" "${SRCROOT}/.." "${SRCROOT}/tmp.xcconfig"

Biplovkumar · 2024-02-09T05:00:00Z

Just u

This is not a solution

bigriot · 2024-02-10T08:07:56Z

Anything speaking against doing it like this:

rm -rf "${SRCROOT}/../node_modules/react-native-config/ios/ReactNativeConfig/GeneratedDotEnv.m"
cp "${PROJECT_DIR}/../.env.development" "${PROJECT_DIR}/../.env"  
"${SRCROOT}/../node_modules/react-native-config/ios/ReactNativeConfig/BuildXCConfig.rb" "${SRCROOT}/.." "${SRCROOT}/tmp.xcconfig"

I think this is pretty much it. A simple update to the documentation would suffice IMHO. I would add
rm "${SRCROOT}/tmp.xcconfig"
as a post action script or add tmp.xcconfig to .gitignore

endrits079 · 2024-02-22T13:58:45Z

Why is this closed when this issue apparently still exists?

phuocantd · 2024-02-29T17:37:28Z

@mickael-h Faced the same issue, fixed it by clearing the xcodederiveddata in your system.

This works for me. To be more specific, I added the following script to my package.json, which I run every time I change the contents of my .env file:
"deleteDerivedData": "rm -rf ${HOME}/Library/Developer/Xcode/DerivedData/*"
I am using different schemes in my project which means I have a .env.prod, .env.develop, and .env.qa file, the contents of which are copied into the main .env file when running the associated scheme. I always delete derived data before switching the scheme I'm running locally.

It not work for me

samipshresthaq · 2024-04-06T04:31:05Z

Faced the same issue, every time need to manually remove node_modules/react-native-config/ios/ReactNativeConfig/GeneratedDotEnv.m.
Any updates on the handling?

i fixed this issue using this #698 (comment)

This worked for me on ios! Apr 6 2024

sergsar · 2024-04-28T23:41:44Z

The issue still exists on iOS and deleting .env files every build isn't a good idea at all

arelstone · 2024-04-29T05:21:31Z

The problem is not the env file nor the xcode cache. The problem is that a file is written into the ios and android directories of this library.

A workaround that I am using is to create a prestart script in our package.json that deleted thoes files

"prestart": "rm -f node_modules/react-native-config/ios/ReactNativeConfig/GeneratedDotEnv.m node_modules/react-native-config/android/build/generated/source/buildConfig/debug/com/lugg/RNCConfig/BuildConfig.java node_modules/react-native-config/android/build/generated/source/buildConfig/release/com/lugg/RNCConfig/BuildConfig.java"

This requires us to restart the metro bundler when we've updated the env - Which to me makes sense.

valerii-link · 2024-05-07T09:08:56Z

#788 (comment)

eisodev · 2024-07-11T10:41:23Z

From reading the comments, this works for me when I change a custom ENV variable URL from server to localhost for running a local backend and then starting my React Native app (following is from my "scripts" in package.json:

"refreshENVforiOS": "touch \"node_modules/react-native-config/ios/ReactNativeConfig/BuildDotenvConfig.rb\"",
"ios": "npm run refreshENVforiOS && react-native run-ios --terminal terminal",

npm run ios

Starts a new terminal window (like it used to before newer React Native versions). And it now reads the correct env variables that I updated in the .env file in the project root.

Yangeok · 2024-08-14T06:08:52Z

Script prestart is the charm! Thank you

khanh21011999 · 2024-11-05T11:56:22Z

You saved me from stupid dog shit I faced 2 days

#788 (comment)

You saved me from stupid dog shit 2 day, thank god

rafaelmaeuer mentioned this issue Dec 7, 2022

GeneratedInfoPlistDotEnv.h not updated on cmd-builds (iOS) #710

Open

luancurti closed this as completed Jan 11, 2023

Parveshdhull mentioned this issue Feb 29, 2024

Configuration not updating on updating new key in env status-im/status-mobile#19063

Open

BrianMay-AO mentioned this issue Mar 5, 2024

fix(iOS): #698 Re-generate env file on each build #784

Open

valerii-link added a commit to valerii-link/react-native-config that referenced this issue May 7, 2024

fix(iOS): lugg#591 track env file changes on each build

b7832d5

valerii-link mentioned this issue May 7, 2024

fix(iOS): #591 track env file changes on each build #801

Open

Modified variables are not updated after rebuilding #591

Modified variables are not updated after rebuilding #591

Comments

mickael-h commented Jun 27, 2021 • edited Loading

VinitSarvade commented Jul 16, 2021

hke-ghtest2 commented Oct 18, 2022

pvroosendaal commented Nov 4, 2022 • edited Loading

hke-ghtest2 commented Nov 8, 2022

billnbell commented Nov 13, 2022

billnbell commented Nov 13, 2022 • edited Loading

Stas-Buzunko commented Dec 9, 2022

luancurti commented Jan 11, 2023

robsonos commented Jan 12, 2023

alessioemireni commented Jan 12, 2023 • edited Loading

rivaros commented Jan 20, 2023 • edited Loading

dks333 commented Jan 28, 2023

marcoj commented Feb 3, 2023

TwistedMinda commented Feb 6, 2023

billnbell commented Feb 6, 2023

TwistedMinda commented Feb 14, 2023 • edited Loading

lclarkg18 commented Feb 16, 2023

chdzma commented Feb 21, 2023 • edited Loading

billnbell commented Feb 22, 2023

nghiaklabs commented Mar 8, 2023

gCardinal commented Mar 8, 2023 • edited Loading

engineerStuardo commented Mar 11, 2023

billnbell commented Mar 11, 2023

engineerStuardo commented Mar 11, 2023

gCardinal commented Mar 11, 2023

engineerStuardo commented Mar 11, 2023

jackkrone commented Apr 10, 2023

arundevkv commented May 3, 2023

toorandroidmaster commented Jun 10, 2023

Irfanwani commented Jul 11, 2023 • edited Loading

billnbell commented Jul 11, 2023

developerdanx commented Jul 15, 2023

billnbell commented Jul 15, 2023

nathantew14 commented Jul 17, 2023

bodiavaleur commented Jul 21, 2023 • edited Loading

nathantew14 commented Aug 11, 2023

Biplovkumar commented Sep 7, 2023

joaquinvaz commented Oct 2, 2023

nathantew14 commented Oct 5, 2023 • edited Loading

henaharon commented Nov 28, 2023 • edited Loading

rolfen commented Jan 17, 2024 • edited Loading

arelstone commented Jan 22, 2024

brunovollmer commented Feb 8, 2024

Biplovkumar commented Feb 9, 2024

bigriot commented Feb 10, 2024 • edited Loading

endrits079 commented Feb 22, 2024

phuocantd commented Feb 29, 2024

samipshresthaq commented Apr 6, 2024 • edited Loading

sergsar commented Apr 28, 2024

arelstone commented Apr 29, 2024

valerii-link commented May 7, 2024

eisodev commented Jul 11, 2024 • edited Loading

Yangeok commented Aug 14, 2024

khanh21011999 commented Nov 5, 2024

mickael-h commented Jun 27, 2021 •

edited

Loading

pvroosendaal commented Nov 4, 2022 •

edited

Loading

billnbell commented Nov 13, 2022 •

edited

Loading

alessioemireni commented Jan 12, 2023 •

edited

Loading

rivaros commented Jan 20, 2023 •

edited

Loading

TwistedMinda commented Feb 14, 2023 •

edited

Loading

chdzma commented Feb 21, 2023 •

edited

Loading

gCardinal commented Mar 8, 2023 •

edited

Loading

Irfanwani commented Jul 11, 2023 •

edited

Loading

bodiavaleur commented Jul 21, 2023 •

edited

Loading

nathantew14 commented Oct 5, 2023 •

edited

Loading

henaharon commented Nov 28, 2023 •

edited

Loading

rolfen commented Jan 17, 2024 •

edited

Loading

bigriot commented Feb 10, 2024 •

edited

Loading

samipshresthaq commented Apr 6, 2024 •

edited

Loading

eisodev commented Jul 11, 2024 •

edited

Loading