Crash Log

Deathrowboat

Approved user
Joined
Dec 16, 2014
Messages
30
These are screen shots of the crashes I have encountered in the last 24hrs.I hope this helps.
Screenshot_2014-12-18-09-29-27.pngPhone Info
Screenshot_2014-12-17-22-58-34.pngEnd of a battle
Screenshot_2014-12-17-22-40-50.pngIn chat
Screenshot_2014-12-18-07-27-20.png Searching for a battle
Screenshot_2014-12-18-06-37-47.pngDuring a Battle (frowny face haha)
Screenshot_2014-12-18-06-32-35.png General play
 

Attachments

  • Screenshot_2014-12-17-22-58-34.png
    Screenshot_2014-12-17-22-58-34.png
    53.9 KB · Views: 52
G

Guest

Guest
Hi, Deathrowboat -- thank you for including this detailed information! I'll share this with the game team in hope that it helps them identify a resolution! We apologize for the inconvenience! Hopefully, the game team can push a fix soon!
 

Messiah

Approved user
Joined
Dec 13, 2014
Messages
17
Recipe for failure

Hi guys, I want to express my concern about the continuous connection problems, hope you fix them before the global release. I can't avoid to compare what happened with your other game orcs vs humans: that game has very nice graphics and lots of creativity, it's clear the development team work hard in this area. However that game suffered from heavy crashes and problem connections at the beginning, the result? The game has only bad ratings in the play store and looks like nobody is playing anymore, totally abandoned. No matter how perfect a game can be if you can't play it . Hope you guys have learnt that lesson and don't spoil yourselves the great Dominations.
 

DanQ

Approved user
Joined
Dec 9, 2014
Messages
148
Error While Playing

While playing this evening, I received the following error message:

"(S) Server OOS - Batch with id: 1418948484.983 returned wtih error! Please restart application Code=501 F:1370, U:7854"

After clicking the 'OK' button I was able to continue playing, but chose to close the application as prompted. (All right, not exactly: it said to restart... heh.)

I have not received such an error before, but I hope it will be of assistance of tracking the source of the bug and squishing it.
 
Top