Major Crash

[FreakySt0rm]

# Building 75% > :run
  # A fatal error has been detected by the Java Runtime Environment:
# Building 75% > :run
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000069a151eb, pid=8248, tid=0x00000000000019ac
#
# JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build 1.8.0_102-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  [jfxwebkit.dll+0xd651eb]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Pokemate - Source\hs_err_pid8248.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
:run FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':run'.
> Process 'command 'C:\Program Files\Java\jdk1.8.0_102\bin\java.exe'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 30.247 secs

[SippieCup]

Niantic just made a change to their servers which seems to have stopped current bots. working on this now with the API team.

[EiTeR94]

possible fix https://github.com/NECROBOTIO/NecroBot/commit/35339c3f527e7f934ae5fae6a7c7aa45e246be32

[MaybeItsRyan]

Thanks for the hard work!

[EiTeR94]

is it fixable doctor? :(

[gffde3]

Potentially fixable but it's related to something all 3rd party is relying on (the API). Looks like Niantic modified the protobuf layer in some way that people are starting to unravel. Keep an eye on this for updates: https://www.reddit.com/r/pokemongodev/comments/4w1cvr/pokemongo_current_api_status/

Latest update from that thread was:

"04/08/2016 - 01:37 GMT+1 : Proto files have not changed and new hashes etc. did not have any effect so far. Our best guess currently is that the requests are cryptographically signed somehow, but we don't know anything for sure yet."

You'll have to wait a while as they figure out what specifically has changed. In the meantime, go outside, catch pokemon. ;)

[EiTeR94]

Okay thank mate, gl hf for all dev ! Do your best

[MDashK]

I'm guessing this is the issue that's preventing the program to find Pokestops on the map? Because mine opens up, logs in, but the map as nothing around... So it just stays there...

[SippieCup]

its fixable just be patient.

[EiTeR94]

Any news about an update for the bot?

[arkdelkaos]

@EiTeR94 Here, you can get updates about the api status :) : https://www.reddit.com/r/pokemongodev/comments/4w1cvr/pokemongo_current_api_status/ ...they've open a github page, btw: https://github.com/pkmngodev/Unknown6

[jdmloki]

It has been figured out, they now have a working API!

[EiTeR94]

@jdmloki you have a bot working?

[jdmloki]

No and I suggest some caution. The API makes it obvious to Niantic you're not using the pokemon go app.

On Aug 7, 2016 4:05 AM, "EiTeR94" notifications@github.com wrote:

@jdmloki https://github.com/jdmloki you have a bot working?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SwipeX/PokeMate/issues/300#issuecomment-238071746, or mute the thread https://github.com/notifications/unsubscribe-auth/ATqfSQ491JLDiaQxajMqV7cwY5m6RSsJks5qdZ_zgaJpZM4JcEUE .

[gsisso]

yes the bot is working just need to update to the latest api #306 ,use the bot at your own risk.

[SippieCup]

I would NOT use the current API at this time. that is why i have not pushed an update. it has a very high chance of getting you banned.

[kylestev]

As @SippieCup has mentioned, it is ill advised to use #306 by two of the three core maintainers of this project. Please be advised before trying it.

[gsisso]

I totally agree with you guys yet if someone want to use it ,he can.

[jdmloki]

A side note most of the devs, are taking a break from working on the API so don't except a change anytime soon.

On Aug 7, 2016 11:45 AM, "gsplash" notifications@github.com wrote:

I totally agree with you guys,yet if someone want to use it ,they can.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SwipeX/PokeMate/issues/300#issuecomment-238093136, or mute the thread https://github.com/notifications/unsubscribe-auth/ATqfSTYWwp72yIUZtDdybH5UuzOsoo1eks5qdguxgaJpZM4JcEUE .

[masterof123]

Can we ask what 'anytime soon' is?

I know how hard it can be to predict such things, but being very broad: how long until we can expect it to be up and running again? Days? Weeks? Months? Never?

[kyleshrader]

@masterof123 well this isn't the api which the devs are taking a break from working on; but i imagine the answer is "whenever they feel like it or someone else steps up"

[SippieCup]

a few days at most. I am pretty burnt out from the debugging at the moment.

[EiTeR94]

@sippiecup why are you saying we have a high chance to get banned ?

[MDashK]

@EiTeR94 Because of this: "This API is not flag-proof. Any account using this API will easily be flagged as not playing through the official app. (...) Altitude for example hasn't been fixed. Also all API requests will appear to Niantic to be coming from IOS users, this is wierd if it is matched with a device which normally runs Android. (...)."

[SippieCup]

Even more than that.

The current API implementation has static fields for device, device identifiers, and sensors. if the API has 5,322 concurrent instances of it, then you have 5,322 accounts running in 5,322 different locations, on the same exact device.

End result: A magical device that is in 5,322 different places while concurrently running the app 5,322 times.

to Niantic, even if they are pants on head idiots, its pretty obvious.

[EiTeR94]

Oh okay and you think niantic will really ban those players who using this ?

[kylestev]

I wouldn't use it if I played the game.

[SippieCup]

Yes. Now that signature checks are active it is almost assured that bans will be coming soon. Thats why I have not pushed the update yet.

[EiTeR94]

I used just one time a bot with the new API, you think niantic will ban me ? Even if use the bot like less than an hour?

[SippieCup]

I'd say that it is likely, however they might only ban users who used it for more than a single session or something. Its hard to say how hard they will be on users.

[EiTeR94]

Okay, really thank for that usefull informations ! You will maybe just save my account, hope i will not get a ban, i just used a cracked version of mygobot for less an hour. I will stop it now until the api is more Safe.

[SippieCup]

As I predicted, the new PKGO version is initalizing new fields. Good news is that means they probably need to update the client every time to find detections now.

Bad news is that it proves we will need a better way of moderating these changes. the current API is now VERY unsafe to use if you care about account safety.

I'm thinking about implementing a callback to a server to check if there is a new pkgo client version before launching the bot. Researching the changes now.

[SippieCup]

New update deemed safe for release.