Passing environment variables to `start-emulator-and-run-tests` arguments causes job to fail as of 2.1.1 about android-orb HOT 5 OPEN

Hi @growse, I've spent some time looking into this over the last few days, and it looks like using this command with environment variables is not currently possible with the state of the orb. Changing it to allow for this usage would require the step to be rewritten and remove other features that have been added to this command, such as running in background. As a result, I am going to backlog this issue for now and keep an eye on it to see how the orb changes in the coming months and revisit it periodically.

from android-orb.

Hi @luzfcb, no there is no update on this currently.

from android-orb.

Hi @growse are you still receiving this issue?

from android-orb.

Yep. See https://app.circleci.com/pipelines/github/owntracks/android/1558/workflows/1a5c499c-e269-4cbc-9e01-5948cd82691c/jobs/5474

from android-orb.

@ryanbourdais, any update on this? Circle-ci does not provide a way to invalidate the cache other than simply renaming the cache key, because of that, I need an easy way without changing the code of the application to invalidate the cache used by restore-gradle-cache-prefix and defines the API version of the android system-image

      - android/start-emulator-and-run-tests:
          restore-gradle-cache-prefix: ${ANDROID_LARGE_CACHE_VERSION}-android-${ANDROID_LARGE_API_VERSION}-large
          system-image: system-images;android-${ANDROID_LARGE_API_VERSION};google_apis;x86_64
          additional-avd-args: --device pixel_5
          avd-name: pixel5_api_31

from android-orb.