tanmay/Regolith
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: use available instead of paused when stopping typing indicator

Browse Source 
Sending 'paused' after the first response caused WhatsApp to stop
relaying subsequent 'composing' presence updates. Using 'available'
keeps the bot in a state where typing indicators work consistently.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
gavrielc
2026-02-13 23:05:36 +02:00
parent 658f6b02d3
commit ae474fd344
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/channels/whatsapp.test.ts
View File

@@ -820,14 +820,14 @@ describe('WhatsAppChannel', () => {
expect(fakeSocket.sendPresenceUpdate).toHaveBeenCalledWith('composing', 'test@g.us');
});
it('sends paused presence when stopping', async () => {
it('sends available presence when stopping', async () => {
const opts = createTestOpts();
const channel = new WhatsAppChannel(opts);
await connectChannel(channel);
await channel.setTyping('test@g.us', false);
expect(fakeSocket.sendPresenceUpdate).toHaveBeenCalledWith('paused', 'test@g.us');
expect(fakeSocket.sendPresenceUpdate).toHaveBeenCalledWith('available', 'test@g.us');
});
it('handles typing indicator failure gracefully', async () => {

2
src/channels/whatsapp.ts
View File

@@ -218,7 +218,7 @@ export class WhatsAppChannel implements Channel {
async setTyping(jid: string, isTyping: boolean): Promise<void> {
try {
await this.sock.sendPresenceUpdate(isTyping ? 'composing' : 'paused', jid);
await this.sock.sendPresenceUpdate(isTyping ? 'composing' : 'available', jid);
} catch (err) {
logger.debug({ jid, err }, 'Failed to update typing status');
}