WhatsApp bridge missing aiohttp dependency issue
Cluster 126358. Data as of
Nothing open on GitHub. Fix merged in #133023 on 5 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #133023. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #133023. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a missing aiohttp dependency in the WhatsApp bridge environment, which causes a silent preflight failure and a repeated 'did not start in 15s' loop. The cluster includes a bug report and related fix attempts to declare the dependency and surface a clearer error.
Open issues0
Open PRs0
Fixes on record
-
#133023 fix(whatsapp): a missing aiohttp no longer loops the bridge forever — PM installs it or a named error stops it (#126358, salvage #131431)
files:
plugins/platforms/whatsapp/adapter.py,tests/gateway/test_whatsapp_connect.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#126358[Bug]: Sealed env after update ships partial messaging extra — no aiohttp, WhatsApp bridge probe fails silently (permanent 'did not start in 15s' loop)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #133023
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 5 Oct 2026