Test Cafe Requires Permission To Record Screen -> but permission is already granted on MAC

What is your Test Scenario?

To be able to record the screen on failures

What is the Current behavior?

Copying from #4684 (which is closed & locked) I recently upgraded my mac to Big Sur, and installed the latest alpha version of TestCafe (1.15.0-aplpha.1). When trying to run testcafe I get

TestCafe requires permission to record the screen. Open 'System Preferences > Security & Privacy > Privacy > Screen Recording' and check 'TestCafe Browser Tools' in the application list.

Press any key to retry.
ERROR UnableToAccessScreenRecordingAPIError: The find-window process cannot access the Screen Recording API.
    at runFindWindowBinary

Screen Recording Permission has already been granted for TestCafe… following the advice in #4684, I have unchecked and rechecked TestCafe Browser Tools + restarted my Mac

Your complete configuration file (if any):

{
  "browsers": ["chrome:headless:emulation:device=iPhone X"],
  "src": "./tests/**/*.js",
  "clientScripts":[
    {
      "module":"axe-core/axe.min.js"
    }
  ],

  "assertionTimeout": 15000,
  "pageLoadTimeout": 30000,
  "selectorTimeout": 15000,

  "disableMultipleWindows": false,

  "quarantineMode": false,
  "skipJsErrors": true,

  "disablePageCaching": true,

  "reporter": [
    {
      "name": "xunit",
      "output": "artifacts/test-results/results.xml"
    },
    {
      "name": "spec"
    }
  ],

  "screenshots": {
    "fullPage": true,
    "takeOnFails": true,
    "pathPattern": "${TEST_ID}/${RUN_ID}_${FILE_INDEX}.png",
    "path": "artifacts/screenshots"
  }
}

Your complete test report:

The "quarantineMode" option from the configuration file will be ignored.
TestCafe requires permission to record the screen. Open 'System Preferences > Security & Privacy > Privacy > Screen Recording' and check 'TestCafe Browser Tools' in the application list.

Press any key to retry.
ERROR UnableToAccessScreenRecordingAPIError: The find-window process cannot access the Screen Recording API.
    at runFindWindowBinary (/Users/rcooper/work/github.com/change/regression-qaa/node_modules/testcafe-browser-tools/src/api/find-window.js:36:19)

Type "testcafe -h" for help.

Screenshots:

<img width="905" alt="Screenshot 2021-05-01 at 3 57 52 PM" src="https://user-images.githubusercontent.com/37812673/116797143-4804f480-aa97-11eb-9f77-2a131a995d76.png">

Steps to Reproduce:

Using Big Sur MacOS, run: testcafe chrome -q passCount=1

Your Environment details:

• testcafe version: 1.15.0-alpha.1
• node.js version: 12.14.1
• command-line arguments: testcafe chrome -q passCount=1
• browser name and version: chrome 90.0
• platform and version: MacOS Big Sur 11.3
• other:

[Aaronius]

Using the minus sign was very important. I do wish this tip were in the message that TestCafe logs to the console.

[liront2]

Solved it. it happens when you grant permission to the globally installed testcafe, instead of the one installed in your node_modules. You can grant permissions to the testcafe under: node_modules/testcafe-browser-tools/bin/mac/TestCafe Browser Tools.app it fixed it for me.