mirror of
https://github.com/alexal1/Insomniac.git
synced 2026-04-26 18:15:54 +03:00
[GH-ISSUE #188] v3.2.0 not working: 32002 Client error: #613
Labels
No labels
bug
duplicate
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Insomniac#613
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sepi2048 on GitHub (Nov 17, 2020).
Original GitHub issue: https://github.com/alexal1/Insomniac/issues/188
So I tried to install v3.2.0 after using v2.2.8 successfully for a while on my Ubuntu 20.04.
After
python3 -m pip install insomniacI added
start.pyto a new folder, made it executable withchmod +x.I ran the command:
python3 start.py --interact @account --follow-percentage 15 --total-likes-limit 150 --device 11111
The app on the device never opens on the device and this is the exception I get:
Caught an exception: -32002 Client error: <> data: Selector [childOrSibling=['child'], childOrSiblingSelector=[{'mask': 8388608, 'childOrSibling': [], 'childOrSiblingSelector': [], 'index': 4}], resourceId='com.instagram.android:id/tab_bar', className='android.widget.LinearLayout'], method: NoneI tried to updated the Android platform tools from 30.0.4 to 30.0.5.
(The v2.2.8 still works from a separate folder.)
Please help!
@mo-tech55 commented on GitHub (Nov 18, 2020):
I have the same issue but it works for me if I have the app active and not closed. But still it does not work if we use the repeat argument because then the app is in the background.
@Sejdra-ing commented on GitHub (Nov 19, 2020):
in the session.py file you can change out the following line:
Change
open_instagram(self.device)
To
close_instagram(device_wrapper.device_id)
that solves the problem while waiting for the fix of this bug in the next version.
@herbertgroff commented on GitHub (Nov 22, 2020):
Same error here, workaround doesnt help but throws new error ;(
@0libar commented on GitHub (Nov 22, 2020):
As strange as it sounds a simple closing/reopenning the app worked for me...
@Fadude commented on GitHub (Nov 23, 2020):
Fixed on v.3.3.2, closing.