pokemons soon planned to add their evolution are not detected correctly when they are nicknamed.

[udnp]

e.g, Piloswine is a pokemon which is planned to add its evolution soon.
Piloswine renamed by users nickname is not detected correctly, like following screen images.
It seems that renamed Piloswine is detected as Mamoswine.
Maybe, this is because GoIV is ready to detect Mamoswine but PokemonGo has not released Mamoswine yet.

[nahojjjen]

Does this still occur? I cant reproduce it on my phone.

[udnp]

Still occurs on my environment.
I've confirmed followings additionally.

a nicknamed 82-Magneton detected as 462-Magnezone.

a nicknamed 282-Gardevoir detected as 475-Gallade.

a nicknamed 362-Glalie detected as 478-Froslass.

[udnp]

It seems that this issue does not always occur for all nicknames.
There are some nicknames which do not cause this issue.

I'll investigate this with Logcat.

[mokahless]

Just confirming this is still an issue in 5.2.8

Nicknamed my Magneton to "DEE" as per above and it is detected as Magnezone.