-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Description
Description
We're seeing different behaviour when using NWBrowser's .bonjour vs .bonjourWithTXTRecord for service discovery, only in CI environments.
It would be good to know why this happens so we can understand if it's a configuration issue with Github Actions or something we can address ourselves.
For clarity, both .bonjour and .bonjourWithTXTRecord work fine when ran on our local machines. Also, using DNSServiceResolve to resolve the TXT records manually rather than rely on .bonjourWithTXTRecord also resolves correctly. The issue seems to be specifically with .bonjourWithTXTRecord when used on a Github Actions runner.
Any further clarification would be much appreciated.
Thanks
Platforms affected
- Azure DevOps
- GitHub Actions - Standard Runners
- GitHub Actions - Larger Runners
Runner images affected
- Ubuntu 22.04
- Ubuntu 24.04
- macOS 13
- macOS 13 Arm64
- macOS 14
- macOS 14 Arm64
- macOS 15
- macOS 15 Arm64
- macOS 26 Arm64
- Windows Server 2019
- Windows Server 2022
- Windows Server 2025
Image version and build link
https://github.com/RobertBlaauboer/bonjour-with-txt-record-repro/actions/runs/18909294466
Is it regression?
No
Expected behavior
Using .bonjourWithTXTRecord returns found services and their TXT records when used on a Github Actions runner.
Actual behavior
When using .bonjourWithTXTRecord no services are found.
Repro steps
Full repro here in Github Actions workflow:
https://github.com/RobertBlaauboer/bonjour-with-txt-record-repro
In short:
Use NWBrowser with .bonjourWithTXTRecord to browse for bonjour services on Github Actions
Note that nothing is found.