"Environment variable not found for field" if build_runner hasn't been run without envied

[jamesncl]

Whenever I create a fresh clone of my project, which uses envied, when I run flutter pub run build_runner build --delete-conflicting-outputs I always get:

Environment variable not found for field accessToken.
package:my_project/env/env.dart:8:23
╷
8 │ static final String accessToken = _Env.accessToken;
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵

The only way I can resolve the problem is to comment out my env.dart file, run build_runner (which succeeds), then restore my env.dart and run build_runner again. Then the problem seems to fix itself. So basically, envied doesn't seem to work if you haven't run build_runner at least once without any envied code.

I'm using Flutter 3.13.1. My variables are stored in a file called .env at the root of my project.

Here's my env.dart:

import 'package:envied/envied.dart';

part 'env.g.dart';

@Envied(path: '.env')
abstract class Env {
  @EnviedField(varName: 'ACCESS_TOKEN', obfuscate: true)
  static final String accessToken = _Env.accessToken;
}

And my .env:

ACCESS_TOKEN=my-token

[DarkHeros09]

yep, i got the same problem.

[DarkHeros09]

Any update on this issue? the package is not working right now.

[✓] Flutter (Channel stable, 3.13.4, on Microsoft Windows [Version 10.0.22621.2283], locale en-US)
    • Flutter version 3.13.4 on channel stable at C:\Users\m_ben\.puro\envs\stable\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 367f9ea16b (11 days ago), 2023-09-12 23:27:53 -0500
    • Engine revision 9064459a8b
    • Dart version 3.1.2
    • DevTools version 2.25.0

[atanasyordanov21]

I have the same problem when adding new variables in my .env file. It always says that the new variable was not found. But as @jamesncl proposed, if I comment out the entire env.dart file (as if it doesn't exist at all), then run build_runner, then bring back env.dart (remove comments), then again build_runner - everything comes to its place. Anyway thanks for the great plugin!

[Saeeed-B]

@atanasyordanov21 not this is not solution , and not workig.

[Saeeed-B]

@petercinibulk please see this issue

[sonjz]

The issue is a known build_runner cache related issue, there are 2 fixes:

this is a hammer:

• run flutter clean before running build_runner Changes in .env file does not update generated env files #6 (comment)

more delicate:

• or run build_runner clean before build_runner build --delete-conflicting-outputs Changes in .env file does not update generated env files #6 (comment)

[techouse]

Duplicate of #6

[jamesncl]

build_runner clean does appear to be a workaround, thanks. Should this be added to the envied README? Because as far as I can tell this package is essentially unusable without this crucial piece of knowledge. Alternatively, this issue and #6 should be left open until the root cause is fixed, so others can understand and find the workaround.

[techouse]

Should this be added to the envied README?

Good idea! Added in #77

[lionseye009]

import 'dart:io';

main() {
Directory current = Directory.current;

print(current);
print(current.path);
}

Run this to get your root path, it will be much longer.

I had to use this:
@envied(path: '/home/username/Development/dart_test_project/bin/env/.env')