You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
dotenv CI/CD: XCode Cloud - how to define env vars ? Android appbundle - how to define env vars ? #97
changed the title [-]dotenv CI/CD: XCode Cloud - how to define env vars ? Android appBuild - how to define env vars ?[/-][+]dotenv CI/CD: XCode Cloud - how to define env vars ? Android appbundle - how to define env vars ?[/+]on Jan 24, 2024
I'm facing the same issue with a different use case.
I'm trying to run flutter test on Github actions without loading the .env into my repo.
My tests fail because the pubspec.yaml is expecting a .env file at the expected location. The command did not even touch test settings or any test file.
one can reproduce this situation locally, by temporarily removing the .env or changing the name) from their project and trying to run their tests.
Reacted by Mahdiyar Arbabzi, Stephan Korner, Kosrat Ahmed and Manuel Santos Souza
I'm facing the same issue with a different use case. I'm trying to run flutter test on Github actions without loading the .env into my repo. My tests fail because the pubspec.yaml is expecting a .env file at the expected location. The command did not even touch test settings or any test file.
one can reproduce this situation locally, by temporarily removing the .env or changing the name) from their project and trying to run their tests.
Activity
[-]dotenv CI/CD: XCode Cloud - how to define env vars ? Android appBuild - how to define env vars ?[/-][+]dotenv CI/CD: XCode Cloud - how to define env vars ? Android appbundle - how to define env vars ?[/+]BirgitPohl commentedon Feb 5, 2024
I'm facing the same issue with a different use case.
I'm trying to run
flutter teston Github actions without loading the .env into my repo.My tests fail because the pubspec.yaml is expecting a .env file at the expected location. The command did not even touch test settings or any test file.
one can reproduce this situation locally, by temporarily removing the .env or changing the name) from their project and trying to run their tests.
mahdiyarz commentedon Feb 10, 2024
I have the same issue too!