Skip to content
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

Application stops when an account sets "Message request" feature on. #10

Open
Omeralbayrak17 opened this issue Jan 22, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Omeralbayrak17
Copy link

Describe the bug
This bug happens when a user sets their "get only dm messages from connected accounts" feature true. When this happens, the app gets confused and does not turn anything back.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'add users' and add an user with the feature I said enabled and add normal accounts for testing purpose.
  2. Start sending a message to all the accounts we added.
  3. Then application will send message to the account that have "get dms from only connected accounts"
  4. And you will see our error, which is raise exception_class(message, screen, stacktrace)
    selenium.common.exceptions.StaleElementReferenceException: Message: stale element reference: stale element not found

Expected behavior
We could expect application sending dm to that account and still send dms to other accounts we added.

Desktop (please complete the following information):

  • OS: Windows
  • Version 10

Additional context
This happens when an account we DM'd uses an instagram feature called "message requests". This means the person we DM'd should accept our message invite then see our message. This thing causes the problem in the application.

@Omeralbayrak17 Omeralbayrak17 added the bug Something isn't working label Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant