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:
Go to 'add users' and add an user with the feature I said enabled and add normal accounts for testing purpose.
Start sending a message to all the accounts we added.
Then application will send message to the account that have "get dms from only connected accounts"
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.
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:
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):
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.