fix(google-chat): don't flip clarify to text-capture at send time
mark_awaiting_text is the 'Other (type answer)' mode-flip, not a send-time setup call — invoking it in send_clarify forces the user's next message to be captured as the clarify response, racing the button-click path and bypassing the buttons entirely. Telegram calls it only in the 'other' callback branch; do the same here.fix/verification-admin-route-recovery
parent
09505a393e
commit
fce298f700
|
|
@ -2103,12 +2103,6 @@ class GoogleChatAdapter(BasePlatformAdapter):
|
||||||
result = await self.send_card(chat_id, card, metadata=metadata)
|
result = await self.send_card(chat_id, card, metadata=metadata)
|
||||||
if result.success:
|
if result.success:
|
||||||
self._clarify_state[clarify_id] = session_key
|
self._clarify_state[clarify_id] = session_key
|
||||||
try:
|
|
||||||
from tools.clarify_gateway import mark_awaiting_text
|
|
||||||
|
|
||||||
mark_awaiting_text(clarify_id)
|
|
||||||
except Exception as exc:
|
|
||||||
logger.warning("[GoogleChat] mark_awaiting_text failed: %s", exc)
|
|
||||||
return result
|
return result
|
||||||
return await super().send_clarify(
|
return await super().send_clarify(
|
||||||
chat_id, question, choices, clarify_id, session_key, metadata
|
chat_id, question, choices, clarify_id, session_key, metadata
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue