Why did my ZA Pokedex have Shiny Baxcalibur registered?

Question

When I first caught a Baxcalibur, it was not shiny, but when I checked its page, it had the shiny option. On no other page has this happened (and I've been making a living dex, so I've checked them a lot).

I have since caught a shiny one, but about 2 weeks after this happend, and forgot about it until then.

Comments

I don't have ZA so not sure if this is how it works, but did you see one in an online battle?

---

No, I've seen way more shinies in online battles, and none of them (h goodra for instance) are shiny in my dex

---

Wait you battled FieryHalmar recently, correct? Did he have a Baxcalibur?
Or, were you traded one?

---

Flagged because of the following:
- two weeks ago
- have got a shiny since then
- zero proof of this occurring
- have engaged online
It seems highly likely you misremembered at least one aspect, making it impossible to tell. Even if you didn’t, it doesn’t seem like you have any proof or photos of this occurring.

---

No, none of it being traded or encountered happened. I say I have bad short term memory - in forgetting to post it -  but good long term memory, so I am confident the appearance did happen, and being traded one didn't.
I can close this if you want, but I made it in case someone else who had the same experience, or was familiar with ZA's code, could tell me why it had.
All this to say, tell me to hide it if you want, since you have valid reasons, but I just made this because I was curious about something I remembered happening.

---

For what it's worth, there are a lot of minor Pokedex bugs with the DLC. I have encountered one myself (Raichu's shiny megas were unavailable even though I only owned shiny Raichu) and I've heard other people have similar issues with shinies either showing up or not showing up.
I can't say for sure, but I wouldn't be surprised if it's just another one of those.

---

I’m fine leaving this post open for now since the game is still being documented and like Hex said, this could be a bug. But if there’s no real reason in time as for why this happened, then I’d want this to be closed under unexplainable behaviour with no evidence