Seen throughout the 2026-07-15 real-device e2e (app created, scopes granted, v1.0.0 released — p2p loop fully working):
WARN magpie::platforms::feishu: connect: feishu bot/v3/info failed
(bot/v3/info response missing open_id); group messages will be
treated as unmentioned (dropped) until this succeeds
The GET /open-apis/bot/v3/info call succeeds but our parse finds no open_id, so bot_open_id stays None and every group message is dropped as unmentioned. Needs investigation against the real response shape — candidates: the field lives under bot.open_id (nested envelope), or the payload only carries app_name/activate_status until some extra condition, or the open id is exposed under a different key. Also worth a retry: it's fetched once in start() and never again (the doc comment says 'until this succeeds' but nothing retries it).
Note: the in-proc bamboo adapter (connect/platforms/feishu) shares this code shape — whatever the fix is, port it both ways (same as #3 ↔ bamboo#484).
https://claude.ai/code/session_014iw5PBsSzDFHus1GfkAK4y
Seen throughout the 2026-07-15 real-device e2e (app created, scopes granted, v1.0.0 released — p2p loop fully working):
The GET /open-apis/bot/v3/info call succeeds but our parse finds no
open_id, sobot_open_idstaysNoneand every group message is dropped as unmentioned. Needs investigation against the real response shape — candidates: the field lives underbot.open_id(nested envelope), or the payload only carriesapp_name/activate_statusuntil some extra condition, or the open id is exposed under a different key. Also worth a retry: it's fetched once instart()and never again (the doc comment says 'until this succeeds' but nothing retries it).Note: the in-proc bamboo adapter (
connect/platforms/feishu) shares this code shape — whatever the fix is, port it both ways (same as #3 ↔ bamboo#484).https://claude.ai/code/session_014iw5PBsSzDFHus1GfkAK4y