Skip to content

fix: add additional sendSeen() argument #3600

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

avoylenko
Copy link

PR Details

Adding second argument for window.Store.SendSeen.sendSeen()

Description

SeedSeen method does mark the chat as seen. Seems like the problem was with missing second argument for the seenSeen function.

Related Issue(s)

Motivation and Context

How Has This Been Tested

By running the loaded service for more than 3 days.

Environment

  • Machine OS:
  • Phone OS:
  • Library Version:
  • WhatsApp Web Version:
  • Puppeteer Version:
  • Browser Type and Version:
  • Node Version:

Types of changes

  • Dependency change
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • My code follows the code style of this project.
  • I have updated the documentation accordingly (index.d.ts).
  • I have updated the usage example accordingly (example.js)

@avoylenko avoylenko changed the title fix: add additional seen argument fix: add additional sendSeen() argument Jun 13, 2025
Copy link
Collaborator

@alechkos alechkos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the problem was with missing second argument for the seenSeen function.

Additional argument does not fix the function.

@avoylenko
Copy link
Author

@alechkos hm, weird then since after adding that argument to the function all messages are being marked as seen again.

@elhumbertoz

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants