[Bug]: MiniMax Code 3.0.67 macOS arm64 latest disables WeChat IM auto push because listBindingsByAgent is not exposed
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
- Ambito
- desktop
Direzione di ricerca
Inizia ispezionando il percorso dell’app impacchettata app.asar e la logica di consegna di cron/delivery.ts descritta nel report, concentrandoti sul fatto che listBindingsByAgent sia esposto e utilizzabile. Riproduci il problema su MiniMax Code 3.0.67 per macOS Apple Silicon con un account WeChat IM associato, quindi confronta il comportamento del pacchetto interessato. Il lavoro è completato quando l’enumerazione dei binding e la consegna automatica su WeChat funzionano, oppure quando il limite intenzionale viene reso chiaramente esplicito.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Version / 版本号
3.0.67
Platform / 平台
macOS
OS version / 系统版本
macOS Apple Silicon / arm64 (exact macOS version not collected)
Issue area / 问题类型
Startup / install / update
Upload ID / 日志上传 ID
not uploaded; local package/hash evidence included
What happened? / 问题描述
MiniMax Code 3.0.67 on macOS Apple Silicon appears to ship with code that disables WeChat IM automatic push delivery. This does not look like a local installation/configuration/account/database issue.
The specific behavior observed in the packaged code is that cron/delivery.ts deliberately does not expose listBindingsByAgent, so the delivery cron path cannot enumerate the IM bindings for an agent and therefore cannot send automatic WeChat pushes.
Local comparison evidence:
- MiniMax logs show that version
3.0.67was downloaded from the official update server andlatestchannel:filecdn.minimax.chat/public/minimax-agent-prod/release
- Installed app package hash:
/Applications/MiniMax Code.app/Contents/Resources/app.asar- hash prefix:
0a062e9b...a1a21a
- Official updater cache zip contains an
app.asarwith the same hash:0a062e9b...a1a21a
- The relevant packaged code path is
cron/delivery.ts, wherelistBindingsByAgentis not exposed, effectively closing the automatic IM push path.
Therefore this can be narrowed to a product-level behavior/regression in the official MiniMax Code 3.0.67 / macOS Apple Silicon / CN prod latest release package, rather than this machine having the wrong database field, wrong WeChat binding, or a locally modified download.
This is different from earlier WeChat QR binding/version-handshake issues. In this case the installed package and official updater cache package are byte-identical for app.asar, and the failure is tied to code shipped in the official 3.0.67 release package.
Steps to reproduce / 复现步骤
- Install or update to MiniMax Code
3.0.67from the official CN prodlatestupdate channel on macOS Apple Silicon. - Ensure WeChat IM has previously been bound or is expected to receive automatic task/session push notifications.
- Trigger a workflow that should produce an automatic WeChat IM notification.
- Observe that the WeChat push is not delivered.
- Inspect the packaged
app.asar/cron/delivery.tscode path and confirm thatlistBindingsByAgentis not exposed to the delivery logic.
Expected behavior / 预期行为
If a user has successfully bound WeChat IM, MiniMax Code should continue to push task/session notifications automatically through WeChat after upgrading to 3.0.67.
At minimum, if WeChat push is intentionally disabled for this release/channel, the app should surface this as a product state instead of silently failing delivery.
Actual behavior / 实际行为
After upgrading to MiniMax Code 3.0.67, WeChat push delivery fails even though the issue is not caused by local binding state or a corrupted local installation.
The packaged delivery path cannot enumerate bindings because listBindingsByAgent is not exposed to cron/delivery.ts / the delivery logic, so WeChat automatic push has no binding list to send to.
Logs or crash report / 日志或崩溃信息
Relevant package/update evidence only; no private logs attached here.
Update source observed in MiniMax logs:
filecdn.minimax.chat/public/minimax-agent-prod/release
Installed package:
/Applications/MiniMax Code.app/Contents/Resources/app.asar
hash prefix: 0a062e9b...a1a21a
Official updater cache zip app.asar:
hash prefix: 0a062e9b...a1a21a
Verified scope so far:
MiniMax Code 3.0.67 / macOS Apple Silicon / CN prod latest.
Whether Windows, Intel Mac, other regions, or other channels behave the same still needs comparison.
Suggested fix:
Please restore the binding enumeration path used by IM delivery, or otherwise expose the equivalent of listBindingsByAgent to the cron delivery module so WeChat automatic push can find the agent bindings again. If the disabling was intentional for this release/channel, please document it in the UI/release notes and provide a replacement path for users who depend on WeChat push notifications.
Screenshots / 截图
No response
Before submitting / 提交前确认
- I have searched existing issues.
- I am using the latest version available to me.
- I have removed sensitive information from logs/screenshots.
- Lingua principale
- TypeScript
- Stelle
- 2k
- Fork
- 250
- Merge medio
- 7h 8m
- PR unite (30g)
- 132
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di MiniMax-AI/minimax-code
-
bug needs-triage tui
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
MiniMax-AI/minimax-code#393 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
bug cli documentation needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
MiniMax-AI/minimax-code#299 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
bug cli needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
MiniMax-AI/minimax-code#128 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
bug desktop
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
MiniMax-AI/minimax-code#87 · 2 commenti · 2 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
bug desktop needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
MiniMax-AI/minimax-code#80 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di MiniMax-AI/minimax-code
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
solana-foundation/solana-com#2245 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
`document.cookie` with `max-age=0` does not delete the cookieForse già presa @BartInTheField l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
capricorn86/happy-dom#2460 ·
I maintainer di solito rispondono entro 2 giorni