PoGo is a no-go; API changes break the Windows 10 Mobile Pokémon GO client

It was less than a week ago that PoGo-UWP landed on Windows 10 Mobile. After over 102,000 signatures were collected on a Change.org petition, Windows phone users finally had their Pokémon GO client. Sure, you had to jump through a few hoops to get it, but once you did, you were free to catch them all.

Evidently, that's assuming that you can catch them all within about five days. The developer Kaankehh said that Niantic has updated its server, breaking the API. He is also not anticipating a fix for the issue, so the app is presumably dead.

In a post on GitHub, Kaankehh said the following:

Hey guys,

Like you already know the PoGo app doesn't work.
The reason for that is that Niantic updated their server.
The update ruined the API, the requests are now cryptographically signed.
The latest update was forced so the app could read it.

Does this mean that it is over?
No, the makers of the API are looking in to this, it is not sure if they can fix it.

What do you say? Is it over in your opinion?
Sadly, yes. I dont think that the API creators will be able to decrypt it and if they will be able to get it to work, Niantic will probably add more encryptions. This is probably one of the I don't know how many encryption they will add.

We have to wait till the API creators have more news, I will keep you updated.
Or, you can look by yourself.

As noted, it is entirely possible that Niantic will fix the issue causing this, or at least offer the app what it needs to work; however, it doesn't say much when the developer of PoGo-UWP is not anticipating a solution.

Niantic recently set out to shut down third-party maps apps, such as the Windows app Find 'Em All. While PoGo-UWP might not be seen as "cheating", it could be seen as infringing on the company's trademarks.

Source: GitHub via Windows Central

Report a problem with article
Next Article

Nintendo UK is giving away a Nintendo Classic Mini

Previous Article

Windows 10 now notifies users that Chrome drains the battery faster than Edge

10 Comments - Add comment