As not every user are experiencing this issue and its only related to the chat function of Hearthstone, could the “chat history” of these users bugged at some point in the past?
This question comes from the fact that [battle.net](http://battle.net) app (iOS) and software (PC) have access to previous chat history (which I guess through download).
- Could Hearthstone try to link the new chat session with the chat history and fails at the step of retrieving/linking it?
- Could Hearthstone manage to link sucessfully to the chat history, but would download a bug registered in it causing the game to crash?
Regarding the second possibility, could it be that such a bug have been triggered by Hearthstone simply crashing/disconnecting with the chat box opened and text entered in it? If that’s the case:
I. Could the server be “pre-storing” the text to send (as soon as it is entered in the chat box) and it would be recorded by it as “temporary data” so launching Hearthstone after “The crash” (which would create the bug) and trying to open the chat box might results in having Hearthstone trying to resume/link to chat history, but as “temporary data” would of been saved on the server and that maybe Hearthstone is not designed to link to “temporary data”, Hearthstone wouldn’t be able to resume the chat session and crash?
II. If the iDevice reached 0% battery while Hearthstone chat box is opened with text in it, could Hearthstone not consider this as a crash and thus create no log about premature shut down or the iOS would take over Hearthstone’s behaviour and freeze it from recording any data on the causes of “That shutdown” (which would create the bug)? Thus such shut down would leave no trace of the initial bug creation and again “temporary data” that could of been stored on the server would be unable to be retrieved when opening the chat box as again Hearthstone could not be designed to retrieve those kind of data from the chat history and would result in the game crashing? (As logs should rapidly point to the problem)…
As a suggestion, maybe somehow reseting the chat history from Blizzard’s end would fix this “undetectable bug”?
Thank you