eas update

[lindanip]

Hey

We are having issues with updating environment variable, when using eas update.

We have ran: API="" STAGE="" eas udpate --profile pre-development --message ""

It was only able to change our environment variables once, then it stopped working, we've updated several times and only the text/ui in the app changes but not the environment variables.

And somehow our apollo-graphql initialisation file has different environment variables as compared to our login page, and they both access env values via process.env.VALUE.

for our environment variables we are using: babel-plugin-transform-inline-environment-variables ^0.4.4

We are using SDK 45 eas cli 0.52.0 node v16.16.0 expo-updates ~0.13.4 react 17.0.2 react native 0.68.2

Please adivse.

[stovmascript]

I don't think the eas update currently accepts the --profile flag. It would be great if it did though. Also, if it could be set up in a similar fashion as build and submit in eas.json, with profiles and environment variables, etc.

[lindanip]

Oh ye sorry about that, I meant to put API_URL="" eas --branch pre-development --message ""

1. Just to add on the query above, we have also tried using Expos way of accessing envs, using: Constants.expoConfig.extra.API_URL and it doesn`t work.

When we put console logs on the app.config.js, we are able to see our variables, even on expo dashboard log under Read app config we are able to see them,

But the Constants.expoConfig.extra.API_URL doesn't work

on the code it says expoConfig doesn't exist on the module.

[lindanip]

API="" STAGE="" eas udpate --branch pre-development --message ""

[expo-bot]

Hi there! It looks like your issue requires a minimal reproducible example, but it is invalid or absent. Please prepare such an example and share it in a new issue.

The best way to get attention to your issue is to provide a clean and easy way for a developer to reproduce the issue on their own machine. Please do not provide your entire project, or a project with more code than is necessary to reproduce the issue.

A side benefit of going through the process of narrowing down the minimal amount of code needed to reproduce the issue is that you may get lucky and discover that the bug is due to a mistake in your application code that you can quickly fix on your own.

Resources

• "How to create a Minimal, Reproducible Example"
• "How to narrow down the source of an error"

Common concerns

"I've only been able to reproduce it in private, proprietary code"

You may not have spent enough time narrowing down the root cause of the issue. Try out the techniques discussed in this manual debugging guide to learn how to isolate the problem from the rest of your codebase.

"I didn't have time to create one"

That's understandable, it can take some time to prepare. We ask that you hold off on filing an issue until you are able to fully complete the required fields in the issue template.

"You can reproduce it by yourself by creating a project and following these steps"

This is useful knowledge, but it's still valuable to have the resulting project that is produced from running the steps, where you have verified you can reproduce the issue.

[douglowder]

To work on this, we would need a project that reproduces the issue. It may be that the real problem is in babel-plugin-transform-inline-environment-variables, but it is hard to tell without a working repro.