Action just hangs on setup

[romainmenke]

Run browserstack/github-actions/setup-local@master
with:
  local-testing: start
  local-identifier: random
  local-logging-level: false
  env:
    GOROOT: /opt/hostedtoolcache/go/1.18.3/x64
    BROWSERSTACK_USERNAME: ...
    BROWSERSTACK_ACCESS_KEY: ...
    BROWSERSTACK_PROJECT_NAME: web-tests
    BROWSERSTACK_BUILD_NAME: schedule [Workflow: 1472]
Setting Environment Variables
  BROWSERSTACK_LOCAL_IDENTIFIER environment variable set as:...
  Use BROWSERSTACK_LOCAL_IDENTIFIER env variable in your test script as the local identifier
Downloading BrowserStackLocal binary...
/usr/bin/unzip -q /home/runner/_work/binary/LocalBinaryFolder/linux/binaryZip
BrowserStackLocal binary downloaded & extracted successfuly at: /home/runner/_work/binary/LocalBinaryFolder/linux
Starting local tunnel with local-identifier=... in daemon mode...
/opt/hostedtoolcache/BrowserStackLocal/1.0.0/x64/BrowserStackLocal --key *** --only-automate --ci-plugin GitHubAction --local-identifier ... --daemon start

-< HANGS HERE >-

I have no capacity to provide more context or info at this time.
But the issue is immediately clear if you try to use the action.

[tophattom]

I have encountered this same problem. My builds started to hang at the exact same command on 2022-07-01 somewhere between 10:34 UTC (last working build) and 11:27 UTC (first failing build). No changes were made to the CI pipeline between these builds.

[EduardasVerba]

I have also started seeing this issue around the same time, hangs at the exactly the same moment. No changes made in CI either.

[EduardasVerba]

Decided to stop using the action to download the binary file for tunneling and have the browserstack local tunnel setup through the wdio config instead.

What I am using instead is the @wdio/browserstack-service npm package.
You would still need to use the action to setup the environments for the username and access key

- name: 'BrowserStack Env Setup'
   uses: 'browserstack/github-actions/setup-env@master'
   with:
     username:  ${{ secrets.BROWSERSTACK_USERNAME }}
     access-key: ${{ secrets.BROWSERSTACK_ACCESS_KEY }}

If you need to use localIdentifiers I would just create one yourself however you see fit, I just exported it as an environment variable based on the matrix inside the workflow. In my case I exported the variable named BROWSERSTACK_LOCAL_IDENTIFIER

Then in the wdio.conf.js file you can set it up like this:

module.exports = {
    ...
    user: process.env.BROWSERSTACK_USERNAME,
    key: process.env.BROWSERSTACK_ACCESS_KEY,
    services: [[
        'browserstack',
        {
            browserstackLocal: true,
            opts: {
                localIdentifier: process.env.BROWSERSTACK_LOCAL_IDENTIFIER,
            },
        },
    ]],

With this you don't need to manually install the binary file anymore to test locally, or use the browserstack/github-actions/setup-env@master action.

Not sure about your situation, but this worked for me and will use this solution instead.