vinnymac / PokeNurse

💉 A tool for Pokémon Go to aid in transferring and evolving Pokémon
284 stars 55 forks source link

Cannot login after 5 retries with RPC 100 #211

Open vinnymac opened 7 years ago

vinnymac commented 7 years ago

Placeholder for people with this issue

YesThatAllen commented 7 years ago

Here's what I'm seeing when I try to log in using PTC

authenticate.js?6a8b:67 Error: Unsupported version for hashserver: 5704/1.27.04

When running using yarn run devI can see the full error, which is posted here

https://gist.github.com/YesThatAllen/93904f80051cb8a0234e13a9271525c2

EDIT - I'm using a PTC account, on macOS 10.12.13

stayre commented 7 years ago

Same here - both with and without hash. If it matters, I am on MacOS 10.12.3.

lordjoshi commented 7 years ago

I have the problem with Google account on Windows 7. No token. API is 5704.

YesThatAllen commented 7 years ago

I have two development computers. On my laptop, I when I build from the develop branch, I get a failure.

Today I built from my desktop, and the develop branch works (PTC with a key, set to 5704)

vinnymac commented 7 years ago

A lot of variables, could be Niantic, could be the version of yarn building your dependency tree, could be the token service, etc. Not clear what it was in the above case.

criddery commented 7 years ago

Hello, thank you for the hard work in keeping this app going. I love it. I loaded the updated version, but I'm still getting the "Fetching RPC endpoint failed, received status code 100". I am attempting to log in using Google credentials and I see 2 new inputs (Token and API). Seems API is defaulted in, but I do not know what to use for a Token. Thank you - Colleen

Redarion commented 7 years ago

@criddery they are working on a fix on that thing. Anyway, the Token is an HashKey you can find on the net, even free or paid, but I suggest you to read more about what they are here

truonghnguyen1234 commented 7 years ago

I purchased a HashKey and put it into the login, but I am still getting the failed notification. Is there another step that needs to be made?

hacknug commented 7 years ago

@truonghnguyen1234 You could try the develop branch where most issues have been fixed or wait for a release to come out soon.

truonghnguyen1234 commented 7 years ago

@hacknug I'm not tech savvy enough to figure it out so I guess I'll just have to wait. :(

vinnymac commented 7 years ago

@truonghnguyen1234 shouldn't be long now. A release will be out this week for sure. We are just trying to iron out a few more details with evolve/transfer to make sure that users can actually use the number one features again.

Redarion commented 7 years ago

Just few more hours: next release is in progress!

truonghnguyen1234 commented 7 years ago

@vinnymac So I downloaded the new version, and even with the key, the error comes up. Am I missing something?

ghost commented 7 years ago

Same issue still persists.

image

vinnymac commented 7 years ago

@truonghnguyen1234 @therealabradolf well I didn't close this issue yet did I 😜

We are investigating if it is an issue with the production builds. It looks like @YesThatAllen has his builds working as they are supposed to, so I might just reupload his if I can confirm they are good. It looks like both mac and windows builds are having this issue right now.

truonghnguyen1234 commented 7 years ago

@vinnymac Whoops! Got to excited seeing that update notification. Will hold on until official confirmation! Thank you!

vinnymac commented 7 years ago

@truonghnguyen1234 @therealabradolf I removed the old builds, I am reuploading ones that should work right now. Please give it a try whenever you would like 👍

truonghnguyen1234 commented 7 years ago

@vinnymac No luck. :(

YesThatAllen commented 7 years ago

The most recent builds are working for me on a Mac. @truonghnguyen1234 let us know what OS isn't working?

hacknug commented 7 years ago

They work on both Windows 10 and macOS for me

vinnymac commented 7 years ago

@truonghnguyen1234 same error, same OS? Any differences at all? We could have you try some other builds too. If you hop on discord maybe we can debug this issue together.

truonghnguyen1234 commented 7 years ago

@vinnymac Yeah, it looks like I'm still having an issue on my end. I'm wondering if I'm just missing a step when I purchased my hashkey. I'm on discord now as truonghnguyen1234 or add me on skype komododragon28@hotmail.com

mhastrich commented 7 years ago

Still not working for me on Windows 7 / Google Login / no Token. I will try to Login with Token later.

hacknug commented 7 years ago

@mhastrich if by token you mean hashing key, there's no way you can log in without one. That's expected behaviour.

mhastrich commented 7 years ago

@mhastrich if by token you mean hashing key, there's no way you can log in without one. That's expected behaviour.

The Login screen says a token is only needed for safer API interactions which means it's optional, doesn't it?

2017_03_24_14_37_47_pokenurse_login

vinnymac commented 7 years ago

@mhastrich yea I mentioned this in the dev chat on discord yesterday.

We already fixed it on develop

Redarion commented 7 years ago

@mhastrich The Login screen says a token is only needed for safer API interactions which means it's optional, doesn't it?

actually now it is required.

mhastrich commented 7 years ago

Is the 150 RPM license enough if you only want to read the IV of your pokemon?

hacknug commented 7 years ago

It is way more than enough 👍

Redarion commented 7 years ago

If you can make more than 150 requests per minute by yourself i'll pay you the greater ones! If you do not use any bot, it's more than enough! With pokenurse is almost impossibile so reach that number of requests.

vinnymac commented 7 years ago

It is certainly not impossible to go over 150 requests a minute but it is unlikely. You could at max do 15 evolves in a minute, and that would require praying to RNGesus. But if you were to simply spam the refresh button again and again, I am sure you could get higher than that.

mhastrich commented 7 years ago

I purchased a key but now i get "Error operation timed out after 4549 ms, 5 tries with error: Bad request to hashing server". I left API open which should use default 5704 which is correct?

Edit: It's working at home now. Perhaps Firewall or it needed some seconds to activate!

YesThatAllen commented 7 years ago

I have an idea today's (April 8th) app & api update will require an update to pokenurse's dependencies.

YesThatAllen commented 7 years ago

In general, this issue is resolved by using API 6100.

There will be times when you can't get your key to work, it may be expired. See Bad request to hashing server (expired key)

A similar issue may come up with the next forced update, time will tell.

stayre commented 7 years ago

As I mentioned, My key had expired, so I bought a new one. The New key is the one with the problem.

On May 11, 2017, at 8:14 PM, Allen Hancock notifications@github.com wrote:

In general, this issue is resolved by using API 6100.

There will be times when you can't get your key to work, it may be expired. See Bad request to hashing server (expired key) https://github.com/vinnymac/PokeNurse/issues/223 A similar issue may come up with the next forced update, time will tell.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vinnymac/PokeNurse/issues/211#issuecomment-300949909, or mute the thread https://github.com/notifications/unsubscribe-auth/AZL32D_SY321-5s5rlM1GjXtrb05a-WCks5r46RIgaJpZM4MblOC.