You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
I noticed even the bot successfully posted the comment on a photo/video/carousell but still seeing "Failed to check if comment succeed." and not counted to the total commented counter/limit.
I manually search the username, went to the specific photo/vide/carousell to check the comment. It is still there, means it is not blocked and posted successfully.
What you expected to happen:
Should detect as succeed and count into the limit.
How to reproduce it (as minimally and precisely as possible):
As long as the bot comment a post (any post).
Anything else we need to know?:
N/A
Environment:
GramAddict version: 3.2.12
Device Model/Emulator Type: Huawei P10 and Samsung Galaxy Tab S7
Android Version: 9 and 13
Instagram Version: 300.0.0.29.110
Discord Ticket ID: *(if submitting crash log)
Relevant Logs:
[03/23 18:17:56] INFO | Write comment: Incredible photo! (interaction.py:635)
[03/23 18:17:56] DEBUG | Single click in (660,1613). Surface: (168-960,1518-1659) (device_facade.py:474)
[03/23 18:17:57] DEBUG | 1.83s sleep (utils.py:467)
[03/23 18:17:59] DEBUG | 0.74s sleep (utils.py:467)
[03/23 18:18:01] DEBUG | Text typed in: 1.91s (device_facade.py:732)
[03/23 18:18:01] DEBUG | 1.68s sleep (utils.py:467)
[03/23 18:18:03] DEBUG | Single click in (1023,1551). Surface: (945-1080,1526-1667) (device_facade.py:474)
[03/23 18:18:04] DEBUG | 2.18s sleep (utils.py:467)
[03/23 18:18:06] DEBUG | Checking for block... (views.py:2120)
[03/23 18:18:09] DEBUG | The keyboard is currently open. Press back to close. (views.py:2176)
[03/23 18:18:09] DEBUG | Press back button. (device_facade.py:131)
[03/23 18:18:09] DEBUG | 0.63s sleep (utils.py:467)
[03/23 18:18:15] WARNING | Failed to check if comment succeed. (interaction.py:667)
[03/23 18:18:15] INFO | Go back to post view. (interaction.py:670)
[03/23 18:18:15] DEBUG | Press back button. (device_facade.py:131)
[03/23 18:18:15] DEBUG | 1.02s sleep (utils.py:467)
[03/23 18:18:16] INFO | Back to profile. (interaction.py:329)
The text was updated successfully, but these errors were encountered:
What happened:
I noticed even the bot successfully posted the comment on a photo/video/carousell but still seeing "Failed to check if comment succeed." and not counted to the total commented counter/limit.
I manually search the username, went to the specific photo/vide/carousell to check the comment. It is still there, means it is not blocked and posted successfully.
What you expected to happen:
Should detect as succeed and count into the limit.
How to reproduce it (as minimally and precisely as possible):
As long as the bot comment a post (any post).
Anything else we need to know?:
N/A
Environment:
Relevant Logs:
[03/23 18:17:56] INFO | Write comment: Incredible photo! (interaction.py:635)
[03/23 18:17:56] DEBUG | Single click in (660,1613). Surface: (168-960,1518-1659) (device_facade.py:474)
[03/23 18:17:57] DEBUG | 1.83s sleep (utils.py:467)
[03/23 18:17:59] DEBUG | 0.74s sleep (utils.py:467)
[03/23 18:18:01] DEBUG | Text typed in: 1.91s (device_facade.py:732)
[03/23 18:18:01] DEBUG | 1.68s sleep (utils.py:467)
[03/23 18:18:03] DEBUG | Single click in (1023,1551). Surface: (945-1080,1526-1667) (device_facade.py:474)
[03/23 18:18:04] DEBUG | 2.18s sleep (utils.py:467)
[03/23 18:18:06] DEBUG | Checking for block... (views.py:2120)
[03/23 18:18:09] DEBUG | The keyboard is currently open. Press back to close. (views.py:2176)
[03/23 18:18:09] DEBUG | Press back button. (device_facade.py:131)
[03/23 18:18:09] DEBUG | 0.63s sleep (utils.py:467)
[03/23 18:18:15] WARNING | Failed to check if comment succeed. (interaction.py:667)
[03/23 18:18:15] INFO | Go back to post view. (interaction.py:670)
[03/23 18:18:15] DEBUG | Press back button. (device_facade.py:131)
[03/23 18:18:15] DEBUG | 1.02s sleep (utils.py:467)
[03/23 18:18:16] INFO | Back to profile. (interaction.py:329)
The text was updated successfully, but these errors were encountered: