v1.5.7-BETA16

Changelog June, 06 2017

• Automatically obtain key from server function
• Fix minor bugs

As PokeSniper v1.5.7-BETA16 you won't need to manually input shared key, the app will obtain the key from our server. Just leave the PokeHash key option blank or empty (if you used previous shared key, just delete it). This will be more easy to use without checking this page every once in a while.

Cheers!
Pokesniper-Android

v1.5.7-BETA15

Changelog May 24, 2017

• Added function to catch all pokemons

Get PokeHash keys
https://github.com/pokesniperandroid/PokeSniper-Android/blob/master/KEYS.md

So, here we go guys and please report if this feature fail to work.

As the keys only have one left, will update key list later with new key. So stay tuned. And if this feature fail, just revert to previous version until there's new update.

Cheers!
PokeSniper-Android

v1.5.7-BETA14

Changelog May 17, 2017

• Update API to 0.63.1
• Add new key

Get PokeHash keys
https://github.com/pokesniperandroid/PokeSniper-Android/blob/master/KEYS.md

Notice
Some users had experienced softban beetwen first snipe and second because Niantic using new technique which is check the encounter coordinates. Cooldoown around 1 hour beetwen catch.

Quoting @Biqueiras

From a Discord Channel....:
Test result came out. To avoid soft ban from sniping, you need 1 hour of cool down between each snipe.
Example: Assume you are at location A, you have been idle for more than 1 hour and there is a Pokémon spawning at location B, which is >10000km away. You can now teleport to B, touch that Pokémon and capture it at B. Since Niantic records your encounter location now, your latest location is at B, not A. Then, you can spin Pokéstop at B without being soft banned. You may return to A or snipe at another distant location C after another hour of wait.
This method is working smoothly after few trials now, but it's risky and your account may be banned by doing so. Feel free to try on testing accounts and give us feedback. 🍀
Last but not least, big thanks to @madymadme for carrying out the test with me.
Update (20min after this announcement): capture at B, not A.
Update (4 hours after this announcement): It may be a bug or a trap set up by Niantic. If you're not sure about what's going on, please wait for our news and never risk your main account on this.
Update (2 days after this announcement): Cool down time is changed from 30 minutes to 1 hour now.

v1.5.7-BETA13

Changelog Apr 9, 2017

• Updated API to 0.61
• Added Poke Ball options

Additional Info
Pokehash keys:
https://github.com/pokesniperandroid/PokeSniper-Android/blob/master/KEYS.md

v1.5.7-BETA12

Changelog Apr 8, 2017

• Fix berry issues (need confirmation)

v1.5.7-BETA11

Changelog Apr 3, 2017

• Updated API to 0.59.1
• Fix berry issues (need confirmation)
• Fix stuck issues (need confirmation)
• Depecrated: Legacy API

Bugs

• SESSION_INVALIDATED will appear sometimes (very very rare), but you just need to hit the snipe button again.

Sorry for the long update, cheers!
PokeSniper Android

v1.5.7-BETA9

Changelog Mar 16, 2017

• Fix API changes
• Legacy API no longer working as of now

(Crashed when you don't have selected berry fruit, use BETA10 instead to fix this)

Sorry for the long update.
PokeSniperAndroid

v1.5.7-BETA10

Changelog Mar 16, 2017

• Fix crashing when you don't have selected berry to catch pokemon.

Warning
As in v0.57.4 update of Pokemon GO app, Niantic seems sending warning message regarding third-party apps, the risk of getting ban is increasing than before. So, use it at your own risk that you could get banned anytime.

PokeSniper-Android

v1.5.7-BETA8

Changelog Mar 6, 2017

• API upstream changes
• Better logging for pokemon names

v1.5.7-BETA7

Changelog Mar 5, 2017

• Fix interrupted operation
• Fix crash when exiting from pokebag (need confirmation)