Error in evolution stack [ProfileLoop Error]

[sundin100]

Description:
I get this error when I put in any stack limit of pokemon to save to evolve.

Steps to reproduce:

Putting a number other than -1 (e.g. 100) in "evolve_stack_limit" variable.

Expected behavior:
Save 100 of the types of pokemon I have listed under "evolve_before_transfer" variable, and then evolve them.

Actual behavior:
Error running loop ProfileLoop, saves all listed pokemon but does not evolve once reached stack limit.

Version:
v0.6.0 (Also happened with previous commits under dev branch)

Operating System:
Windows 10

Java version:
jdk1.8.0_101
jre1.8.0_101

[Taraegon]

Someone close this. Searching "Error running loop BotLoop!" I got 39 issue hits. The devs, trust me on this, do not need any more reports of this unless you think you have a fresh slant on things.

[sundin100]

This is different to BotLoop. I realised that it was when I added more Pokemon to the list "evolve_before_transfer", other than the ones that come listed in the template.

EDIT: Ok, I have added Zubat only now, looks like everything is okay at the moment. Perhaps it's just certain pokemon.

[Mixone-FinallyHere]

Change name of issue to what it is
as in:
Error in evolution stack [ProfileLoop Error]

[ansalls]

Can confirm that the issue is the bot mishandling pokemon added to the stack list.

EDIT: I was mistaken. It just happened to be that I moved further from my router, I think. It's now stopped working again and I tried every combination of settings in the config to no avail. However, I set my uplink to 256kbps and 350ms delay and now it's working as it should, so I'm certain it's an API issue. It presumably is only affecting Macs from the other issues reported, and a hotfix is to install and use the mac Network Link Conditioner to slow the requests to Niantic's server.

[Sieberkev]

Can you test with the most recent version of the development branch? A lot of evolve improvements have been implemented since these posts.

In the next release there will be an update to the underlaying API that should fix the annoying null responses.

[stupiz]

start evo for some and then gone