CICD asks for analytics, no way to opt out

[christian-hess-94]

Is there an existing issue for this?

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

Steps to reproduce

We are pushing a RN update in our app. We use maestro for running visual regression screenshot tests, and the branch that has the update is getting stuck when maestro asks us to opt into analytics:

Actual results

The CICD workflow gets stuck after bundling the app and running maestro, as maestro asks for us to opt into analytics:

Expected results

We would like to know if we can modify the command to run maestro to automatically opt out of analytics (we do not wish to opt in at this point)

About app

The app is closed source. The issue with maestro is happening only when running out visual regression suites via github actions CICD runners.

About environment

The workflow runs on ubuntu, I don't know which specific version

Logs

Logs

BUILD SUCCESSFUL in 11m 46s
983 actionable tasks: 983 executed

Build successful!
Starting emulator...
Waiting for emulator to start...
Installing APK on emulator...
Performing Streamed Install
Success

App installed successfully!
Waiting for the simulator to start...
===== Run E2E Attempt: 1 ====
Maestro CLI would like to collect anonymous usage data to improve the product.
Enable analytics? [Y/n] 
Error: The operation was canceled.

Maestro version

1.33.1

How did you install Maestro?

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

Anything else?

This is the step where we are installing maestro in our CICD machine:

• name: Install Maestro
  run: |
  export MAESTRO_VERSION="1.33.1"
  curl -Ls "https://get.maestro.mobile.dev" | bash

[bartekpacia]

Hey @christian-hess-94, sorry about this!

For now, this should work: printf 'n\n' | maestro <...>

[christian-hess-94]

hi @bartekpacia! Thanks for the response. This is the way we are running the maestro command:

const MAESTRO_TEST_COMMAND = `${process.env.HOME}/.maestro/bin/maestro test .maestro/storybook.yml`;
...
const child = spawn(MAESTRO_TEST_COMMAND , [], { ...options, shell: true });

So i'd change it to:

const MAESTRO_TEST_COMMAND = `printf 'n\n' | ${process.env.HOME}/.maestro/bin/maestro test .maestro/storybook.yml`;
...
const child = spawn(MAESTRO_TEST_COMMAND , [], { ...options, shell: true });`

[bartekpacia]

Hey @christian-hess-94, v1.37.4 is out and this problem should no longer occur on CIs.

To disable analytics collection (and asking for it), set MAESTRO_CLI_NO_ANALYTICS environment variable to any value, for example:

MAESTRO_CLI_NO_ANALYTICS=1

Please let me know if the issue persists.

[christian-hess-94]

awesome thanks for the quick response, I'll try to implement it here and circle back to you!

[christian-hess-94]

@bartekpacia would this work as a way to set the analytics env variable?

So basically setting it during install, so it goes over to when we eventually execute maestro using node

[bartekpacia]

Nope. On GitHub Actions you set env vars in a bit different way - see here

[christian-hess-94]

oh ok got it thanks! I have modified like so:

the yarn test:visual:android line is the script that executes maestro:
"test:visual:android": "node .maestro/scripts/visual-testing.js compareScreenshots --platform=android",

this leads to the code snippets I sent originally:

const MAESTRO_TEST_COMMAND = `${process.env.HOME}/.maestro/bin/maestro test .maestro/storybook.yml`;
...
const child = spawn(MAESTRO_TEST_COMMAND , [], { ...options, shell: true });

does this make sense?

[bartekpacia]

Yes, that should work.

If it solves your problem, please close the issue. Cheers!

[bartekpacia]

This was released in v1.37.4.

If this issue still occurs to you, please comment.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue.
Thank you for helping keep us our issue tracker clean!