(1.39.0) ENV variables are not persisting when set from a pipeline

[nboxill]

Is there an existing issue for this?

• I have searched the existing issues and didn't find mine.

Steps to reproduce

Run maestro test on a flow from a gitlab pipeline - using a shell-script installed runner on the host machine.

Actual results

I have a niche use-case with maestro, with my app i'm using a shell-script gitlab runner to run test flows said runner, on a host machine.

Env variables are set from a pipeline:

- export MAESTRO_TEST_EMAIL="$TEST_EMAIL"

CLI 1.38.1

- inputText: ${MAESTRO_TEST_EMAIL} works

CLI 1.39.0

- inputText: ${MAESTRO_TEST_EMAIL} returns null

Expected results

Expect the env variables to persist in maestro tests when set from a gitlab pipeline.

About app

App is a native android application

About environment

MacOS Sonoma

Logs

Logs

<!-- Replace this line with your logs. *DO NOT* remove the backticks! -->

Maestro version

1.39.0

How did you install Maestro?

install script (https://get.maestro.mobile.dev)

Anything else?

N/A

[linear]

MA-2369 (1.39.0) ENV variables no longer working when set from a pipeline

[arancauchi]

Seeing the same issue

[freak4pc]

We're experiencing the same issue

[Fishbowler]

I've recreated this in a simple example.

https://github.com/Fishbowler/maestro-examples/tree/env_vars/env-vars

(I regret naming the folder and branch the same - sorry about that)

Running run.sh gives:

Running on emulator-5554                                                        
                                                                                
 ║                                                                              
 ║  > Flow: flow                                                                
 ║                                                                              
 ║    ✅   Run test.js                                                          
 ║         Log messages:                                                        
 ║           Running test.js                                                    
 ║           MAESTRO_EXAMPLE: undefined                                         
 ║           The env var $MAESTRO_EXAMPLE should be 'potato' but it is not      
 ║    ✅   Run test.js                                                          
 ║         Log messages:                                                        
 ║           Running test.js                                                    
 ║           MAESTRO_EXAMPLE: undefined                                         
 ║           The env var $MAESTRO_EXAMPLE should be 'potato' but it is not      
 ║    ✅   Run ${console.log('MAESTRO_EXAMPLE:' + MAESTRO_EXAMPLE)}             
 ║         Log messages:                                                        
 ║           MAESTRO_EXAMPLE:$MAESTRO_EXAMPLE 

Log file: maestro.log

[woytekn]

Same here