"Look for and connect to any device on your local network" popup stops TestCafe tests

[yourpchelp]

What is your Scenario?

Hello,
Last Chrome (Version 142.0.7444.135 (Official Build) (arm64)) stops TestCafe tests, because the popup "Look for and connect to any device on your local network" appears every run, and "Allow" button can be clicked only manually.
As far as I understand, every time the TestCafe starts tests on Chrome, TestCafe does not use a normal Chrome profile (Default):
~/Library/Application Support/Google/Chrome/Default/Preferences.

This new session of Chrome creates a temporary profile:
e.g. /var/folders/pb/qyfjc4617qx7jny52zlmmfsc0000gn/T/testcafe/chrome-profile-66470fU/Default/Preferences
This profile is deleted immediately after the tests are completed.

I found one ticket about this problem:
https://stackoverflow.com/questions/79808239/message-look-for-and-connect-to-any-device-on-your-local-network-prevents-test
But the proposed solution is for Windows.
I have MacBook Pro, Apple M2 Pro, macOS Tahoe 26.0.1.

What I already did:
chrome://flags/#local-network-access-check and set "Local Network Access Checks" = Disabled.
System Settings -> Privacy & Security -> Local Network and select "Google Chrome".

These actions didn't help.

How can I remove this popup?
Or how can I programmatically click "Allow" in TestCafe-test?

Some details:
https://developer.chrome.com/blog/local-network-access

Thanks in advance.

What is the Current behavior?

The popup "Look for and connect to any device on your local network" appears every run, and "Allow" button can be clicked only manually.

What is the Expected behavior?

The popup "Look for and connect to any device on your local network" does not appear. or "Allow" button can be clicked programmatically.

What is the public URL of the test page? (attach your complete example)

https://devexpress.github.io/testcafe/example

What is your TestCafe test code?

import { Selector, ClientFunction, t } from 'testcafe';

fixture ('example test')
    .page('https://devexpress.github.io/testcafe/example')

    test('just test', async t => {
        console.log('Hello');
    })

Your complete configuration file

No response

Your complete test report

No response

Screenshots

Steps to Reproduce

1. in package.json

  "scripts": {
    "getversion": "testcafe --version",
    "runtest": "testcafe chrome tests/00_test.js",
  },
  "devDependencies": {
    "testcafe": "^3.7.0",
    .......,
    ...........
  }

2. npm run runtest

TestCafe version

3.7.0

Node.js version

v20.16.0

Command-line arguments

testcafe chrome tests/00_test.js

Browser name(s) and version(s)

Chrome (Version 142.0.7444.135 (Official Build) (arm64))

Platform(s) and version(s)

MacBook Pro, Apple M2 Pro, macOS Tahoe 26.0.1

Other

No response

[liubrian-SIG]

I’m encountering the same issue — it appears to be specific to Chrome version 142, since version 141 was working fine for me.

For basic tests, using the --disable-native-automation flag bypasses the popup successfully. However, it doesn’t work for one of my tests that involves file upload.

[yourpchelp]

I have to use native automation for our tests.

[pgusilic-devops]

The issue already been mentioned here #8446

[yourpchelp]

@pgusilic-devops
Thank you for the reference to #8446.
Unfortunately, it didn't help.
I tried both variants:

1. In command line:
   package.json:
   "scripts": {
   "runtest": "testcafe chrome --disable-features=LocalNetworkAccessChecks example/00_test.js"
   },

2. In Chrome settings:
   Navigate to chrome://flags in your browser.
   Search for "Local Network Access Checks".
   Change the setting to "Disabled" and restart the browser.

[deepanshugoyal1989]

Use disableNativeAutomation: true for testcafe

[pgusilic-devops]

@yourpchelp it doesnt work for you because you're still not using it correctly.
Here is my example:

"test": "testcafe \"chrome --disable-features=LocalNetworkAccessChecks\" ./tests/",

[timeimp]

I tried running this command and it seemed to work for me:

testcafe 'chrome --disable-features=LocalNetworkAccessChecks' test.js --debug-on-fail

Note the single quotes

[yourpchelp]

@pgusilic-devops , @timeimp
Thank you very much for the clarification.
How could I not notice this mistake?
The problem has been solved.

[pgusilic-devops]

@yourpchelp np, the issue was that wihout the quote TestCafe thinks that --disable-features belongs to TestCafe therefore flag ignored. but with quotes testcafe knows it belongs to Chrome and Flag applied

[aleks-pro]

Hello @yourpchelp,

Thank you for reporting the issue. You can track our progress in the following thread. I will close this one as a duplicate.

@pgusilic-devops @timeimp thank you for your collaboration