Pokemon HOME recently underwent an extremely long maintenance to correct a bug with Hyper Training, but now it seems another, more serious error has been discovered.

The error was highlighted by Pokemon dataminer Mattyoukhana, and relates to the Pokemon Nincada and Pokemon HOME‘s anti-cloning system. The bug is triggered when the following conditions are met:

• A Nincada is transferred to Pokemon HOME.
• During the transfer, the Nincada is assigned a specific Tracking Number by Pokemon HOME (the anti-cloning measure).
• When the Nincada is transferred to Pokemon Sword/Shield, it will retain this Tracking Number.
• When players evolve their Nincada with an empty space in their party, it will create a Ninjask and Shedinja with the same Tracking Number as the Nincada.
• Now, when the BOTH newly evolved Ninjask and Shedinja are transferred back into HOME at the same time, the app detects that they both have the same Tracking number and will erase one of them thinking its a clone.

Naturally, this bug only affects Ninjask and Shedinja which were created through these steps. It does not appear to affect Ninjask or Shedinja that were transferred up through Pokemon Bank. As of this writing, it is also not known to affect any other Pokemon, likely due to the Nincada line’s unique evolution method.

That said, this is quite a serious oversight by Game Freak and the Pokemon Company, and they should probably look into adjusting the anti-cloning system to correct this error. We will be sure to bring more details as they come.

What do you think? Let us know in the comments.

[UPDATE]: Testing by Youtuber BLAINES has revealed this same glitch can also cause strange things to happen with Ninjask and Shedinja evolved in Pokemon GO and subsequently transferred into Pokemon HOME (e.g. Ninjask transforming into Shedinja). You can find the video below.