Appearance
Account safety and pacing
The Simulator sends what the Instagram app sends, so the account behaves like an account on a real phone. Whether an account stays healthy under heavy use is still decided by how your program uses it. This page says what the Simulator does for the account and what is your job.
What the Simulator does
- It presents one virtual phone per account, the same every time (
seed, How the Simulator works). - It starts every process with the app's launch, so the account never acts before the app would have woken up (The app process).
- It sends each screen's requests in the app's order, with the app's headers and the app's pauses.
What it cannot decide for you
The Simulator is an up-to-date client, not an anti-ban tool. It cannot know how many actions are too many, how fast is too fast, or which proxy and warm-up an account needs. Those are yours.
Rules that keep an account healthy
- One stable
seedper account. A new phone for an old account looks like a new device logging in. - Launch; never act on a cold session. A stored session that acts with no launch before it is a strong signal. The entries already force the launch, so use
launchfor every later run (Ways to start the app). - Keep the account's own phone when you bring it from another system (Bring an account from another system).
- One proxy per account, and a stable one (Proxy, network and location).
- Space the actions out. Wait between likes, follows and messages with
Effect.sleep, and vary the pace. - Stop on the signals Instagram sends.
IgSpamError,IgRateLimitErrorandIgSentryBlockErrormean slow down or stop; do not retry in a loop (Errors).
Test accounts first
Build and try a program on a test account before the account you care about.
The authenticator key and the password
The authenticator setup key is the account's second factor. Keep it with the password only if your program is the account's only user; otherwise keep them apart (Log in).