Since v3.13.8, `expo r -c` no longer cleans the cache

[superkalo]

I have .env file with environmental variables.

When I update any of the values in there and I run expo r -c, the values get refreshed.

After updating to expo-cli v3.13.8 this is no longer the case. The old .env values remain and I don’t know how to clean the cache else way.

PS: I also tried the alias: expo start --clear, same problem.

  Expo CLI 3.13.8 environment info:
    System:
      OS: macOS Mojave 10.14.6
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 13.9.0 - ~/.nvm/versions/node/v13.9.0/bin/node
      Yarn: 1.22.0 - ~/.nvm/versions/node/v13.9.0/bin/yarn
      npm: 6.13.7 - ~/.nvm/versions/node/v13.9.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Android Studio: 3.5 AI-191.8026.42.35.5900203
      Xcode: 11.0/11A420a - /usr/bin/xcodebuild
    npmPackages:
      expo: 35.0.0 => 35.0.0
      react: 16.8.3 => 16.8.3
      react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8
      react-navigation: 4.0.10 => 4.0.10
    npmGlobalPackages:
      expo-cli: 3.13.8

[superkalo]

I’m still facing the issue with expo-cli v3.15.5

PS: I tried downgrading to v3.12.1 and it’s all good! Must be something you’ve changed in the later versions.

[marcosca]

same issue here. I don’t know a way to refresh the environment variables declared in .env file.

[superkalo]

I’m still facing the issue with expo-cli v 3.17.18

@ccheever , can you please ask someone to take a look. I’ve shared about this problem 27 days ago and I’m starting to get desperate. Am I doing something wrong?

[marcosca]

Same issue here

[superkalo]

@marcosca, as of expo-cli v 3.20.3, this issue is finally silently fixed!!!

Thank you!