Does anyone else have this issue? When I try to update my collection by importing - I get this error. Started last night after Tuesday reset.
"Alert. Unknown battle.net error. We've logged this error and will be looking into it - please check back soon.[/b]"
Cheers
Battle.net Error?
Re: Battle.net Error?
Hi
I am getting the same error too
I am getting the same error too
- Mughal
- Posts:1
- Joined:September 7th, 2012
- Pet Score:13568
- BattleTag®:mughal#1659
- Realm:Mal'Ganis-us
- Contact:
Re: Battle.net Error?
There seems to be an issue with the Blizzard APIs, as the problem is not limited to Warcraftpets but also Wowhead.
- Quintessence
- Posts:2772
- Joined:June 4th, 2008
- Pet Score:14574
- Realm:Proudmoore-us
- Contact:
Re: Battle.net Error?
We're looking into this issue right now, however if it is on Blizzard's end we might have to simply wait for them to address it.
Update: Other fansites are also experiencing trouble importing from the Armory API. Blizzard is aware of the issue and are working on a fix.
Update: Other fansites are also experiencing trouble importing from the Armory API. Blizzard is aware of the issue and are working on a fix.
![Image](http://www.warcraftpets.com/images/quint_forum_sig.png)
Feel free to browse through my pet collecting blog: http://wowpetaddiction.blogspot.com
- Beana
- Posts:249
- Joined:December 27th, 2012
- Pet Score:13784
- BattleTag®:Beana#1484
- Realm:Area 52-us
- Contact:
Re: Battle.net Error?
Whew glad its not just me. Its making it frustrating to name pets though when you don't know the gender.....lol Pet issues ![Very Happy :D](./images/smilies/icon_e_biggrin.gif)
![Very Happy :D](./images/smilies/icon_e_biggrin.gif)
Re: Battle.net Error?
This is also happening to some other sites that make use of the blizzard API. I can't update my collection, and Simple Armory wasn't working for me either >_< I hope they fix it soon.
Re: Battle.net Error?
**edited***
I was getting this earlier today, but it seems to be resolved now. Wonder what keeps causing it?
I was getting this earlier today, but it seems to be resolved now. Wonder what keeps causing it?