Major Jarvee Issues!! (Actions working fine manually)

[So_suave]

Guys, I am seriously confused as to what is going on with Jarvee right now.

Action and temporary blocks on almost every account of mine and they just won't let up. The confusing part is I am able to do actions manually when I use the embedded browser, so it is not an issue with my proxies or accounts (I am using high quality residential proxies and aged accounts that were performing lots of actions before the update).

I'm also getting the blocks right off the bat after 1 or 2 actions, so it is not an issue with my settings either.

I have the option 'Use embedded browser when action blocked' but that doesn't seem to be making a difference either.

Is there something I can do here or is Jarvee completely useless after the update? I have literally tried everything and nothing has been working the past few weeks.

Any help would be much appreciated!!

 

[CuriousAnxiety]

Guys, I am seriously confused as to what is going on with Jarvee right now.

Action and temporary blocks on almost every account of mine and they just won't let up. The confusing part is I am able to do actions manually when I use the embedded browser, so it is not an issue with my proxies or accounts (I am using high quality residential proxies and aged accounts that were performing lots of actions before the update).

I'm also getting the blocks right off the bat after 1 or 2 actions, so it is not an issue with my settings either.

I have the option 'Use embedded browser when action blocked' but that doesn't seem to be making a difference either.

Is there something I can do here or is Jarvee completely useless after the update? I have literally tried everything and nothing has been working the past few weeks.

Any help would be much appreciated!!

I suggest avoid using the API altogether and select the options to use only embedded browser for everything. Or at the very least until Jarvee figure out the API to be less detectable. Try it on a few accounts at least to see if it helps.

 

[So_suave]

I suggest avoid using the API altogether and select the options to use only embedded browser for everything. Or at the very least until Jarvee figure out the API to be less detectable. Try it on a few accounts at least to see if it helps.

Thanks for the suggestion, will try and see if it makes a difference.

 

[Jibri Wright]

I suggest avoid using the API altogether and select the options to use only embedded browser for everything. Or at the very least until Jarvee figure out the API to be less detectable. Try it on a few accounts at least to see if it helps.

The API isn't the issue. That isn't what's being detected, it's the lack of JavaScript running on the client side that's causing the issue. That's why sometimes the embedded browser works. Even so the embedded browser isn't that good of a solution either because a lot of the browser properties aren't spoofed to match a phone. The only thing the embedded browser spoofs is the user agent unfortunately.

 

[GrosseHacker]

I think Jarvee is dead for Insta, set the minimal seeting

 

[CuriousAnxiety]

The API isn't the issue. That isn't what's being detected, it's the lack of JavaScript running on the client side that's causing the issue. That's why sometimes the embedded browser works. Even so the embedded browser isn't that good of a solution either because a lot of the browser properties aren't spoofed to match a phone. The only thing the embedded browser spoofs is the user agent unfortunately.

I've just found that using the EB has stopped any "Your account has been compromised" messages and alleviated the blocks somewhat. We shall see in the coming weeks if Jarvee can solve any of the issues. (But then again we've been saying that for months)

 

[veki971]

Hello, check this video addressing your issues:

 

[So_suave]

I've just found that using the EB has stopped any "Your account has been compromised" messages and alleviated the blocks somewhat. We shall see in the coming weeks if Jarvee can solve any of the issues. (But then again we've been saying that for months)

The API isn't the issue. That isn't what's being detected, it's the lack of JavaScript running on the client side that's causing the issue. That's why sometimes the embedded browser works. Even so the embedded browser isn't that good of a solution either because a lot of the browser properties aren't spoofed to match a phone. The only thing the embedded browser spoofs is the user agent unfortunately.

Looks like its working now on only use embedded browser as CuriousAnxiety suggested. However it only worked on accounts using a 4g proxy (all my sticky residential proxy accounts still have a block).

Will see if the actions continue to run smoothly over the next few days on the embedded browser or not.

Seriously hope Jarvee comes out with a proper update on this soon, no major updates from them yet regarding this issue :-/

 

[So_suave]

I think Jarvee is dead for Insta, set the minimal seeting

It wasn't letting me do even 1 or 2 actions on some accounts, so it is not a settings issue. I think IG is just getting good at figuring out if someone is using a bot like jarvee or not.

 

[proxygo]

jarvees issues started with the last insta updates in june.
after that everything went to crap, and its been terrible since

 

[ilovetobun69]

I suggest avoid using the API altogether and select the options to use only embedded browser for everything. Or at the very least until Jarvee figure out the API to be less detectable. Try it on a few accounts at least to see if it helps.

API works , you just need to be super slow untill it's fixed. Full eb will look suspicious and you will have same issue sooner or later . Idk anyone who uses the browser to view instagram. It's a red flag I'm sure.

jarvees issues started with the last insta updates in june.
after that everything went to crap, and its been terrible since

True but private bots are not much better.

 

[Jibri Wright]

Tbh I'm able to follow 300 a day on all my accounts through FollowLiker, and I believe both FL and Jarvee use the same reverse-engineered private API. The thing is I also have my own bot working in tandem with FollowLiker that logs onto all of my accounts via a browser I programmed to look exactly like a phone browser on the JavaScript side. This way Instagram's JavaScript can pull real-time data on the account like it would if a person were controlling the account. The thing is that FL and Jarvee automate accounts through HTTP requests to Instagram's server directly. They don't have an instance built in where Instagram's JavaScript code can run. You essentially need a browser for that.

 

[TheRekz]

I think Jarvee is dead for Insta, set the minimal seeting

I second this.. manual automation is the way to go, i haven't had issues except a few account compromised, but no blocks

 

[proxygo]

have they rolled any updates for jarvee recently
or just left it in a state of broken-ish limbo

 

[Daddykins]

have they rolled any updates for jarvee recently
or just left it in a state of broken-ish limbo

They sent out an email to all its users that they're not giving up and are testing and working on things. I don't have the email on hand, but it sounded alright. I'm not having too many problems on IG currently using EB. Just do more testing always.

 

[Jerone]

I second this.. manual automation is the way to go, i haven't had issues except a few account compromised, but no blocks

Lol dude said manual automation
Dude tryna act smart ended up contradicting himself

 

[So_suave]

Tbh I'm able to follow 300 a day on all my accounts through FollowLiker, and I believe both FL and Jarvee use the same reverse-engineered private API. The thing is I also have my own bot working in tandem with FollowLiker that logs onto all of my accounts via a browser I programmed to look exactly like a phone browser on the JavaScript side. This way Instagram's JavaScript can pull real-time data on the account like it would if a person were controlling the account. The thing is that FL and Jarvee automate accounts through HTTP requests to Instagram's server directly. They don't have an instance built in where Instagram's JavaScript code can run. You essentially need a browser for that.

Tbh I'm able to follow 300 a day on all my accounts through FollowLiker, and I believe both FL and Jarvee use the same reverse-engineered private API. The thing is I also have my own bot working in tandem with FollowLiker that logs onto all of my accounts via a browser I programmed to look exactly like a phone browser on the JavaScript side. This way Instagram's JavaScript can pull real-time data on the account like it would if a person were controlling the account. The thing is that FL and Jarvee automate accounts through HTTP requests to Instagram's server directly. They don't have an instance built in where Instagram's JavaScript code can run. You essentially need a browser for that.

Mmm wonder why Jarvee would not have implemented that already ? If you were able to program it to look like a phone browser, I would
think their team would be able to do that fairly easily as well.

 

[So_suave]

API works , you just need to be super slow untill it's fixed. Full eb will look suspicious and you will have same issue sooner or later . Idk anyone who uses the browser to view instagram. It's a red flag I'm sure.

True but private bots are not much better.

Yup, embedded browsers worked for a while and then stopped after a few actions. After that PV on more than 4 accounts, I’ve stopped all actions for now. Will rest the accounts and try later.

 

[So_suave]

They sent out an email to all its users that they're not giving up and are testing and working on things. I don't have the email on hand, but it sounded alright. I'm not having too many problems on IG currently using EB. Just do more testing always.

They told me to be patient and wait 1-2 weeks while they try and fix this. Lets see if anything actually happens or if they are just saying to get me to continue using the platform.

 

[proxygo]

lets hope the dont do a gscraper - promise an update
to fix there product then silently slip into obscurity