Disconnection Error 0x04000000
My game has been displaying game error while playing h2h matches it has done this three times in the last hour 😭
CM: Updated thread title for clarity and context.
Forum Discussion
I cannot play even a single match when I get in to the match H2H play for in match 1 minute then the game disconnect me to the match 😭 it will say.
DISCONNECTION ERROR
Disconnection Error0x04000000
Sorry, a game error has occurred that has disconnected you from the match.
I need help please I cannot play with my single match.😭😭😭😭😭😭😭
FC Mobile 27 H2H connection error 0x04000000
Since the FC Mobile 27 update I frequently get disconnected from Division Rivals H2H matches. Sometimes I disconnect and sometimes my opponent disconnects. My internet connection is stable and my ping is good. The error shown is 0x04000000.
Device: Samsung Galaxy M13
Please investigate this issue.
Cómo puedo hacer para que ya no me aparezca eso no me deja jugar en cara cara
FC Mobile, what's going with your servers really? It's a drag and depressing. No point in explaining how excellent my phone is to play this game cause y'all know it's your fault. All my H2H and Manager Mode matches disconnect with the same error besides VA. How's that even possible to begin with? Isn't it supposed to disconnect us from every online match up? This reeks of a sabotage to elite gamers cause what's the point playing this game, buying players and grinding for rewards if one is not to rank up their stars and test their squad against other players??? We deserve a serious compensation of some sort when this is fixed cause our time gets wasted while FC gets the loot.
First of all I want to say thank you for the update ....but I hope from you to solve the bug that happened in division Rivals...the game begins and the error 0×400000 comes again
Yes same here i don't know if it's an illegal script from the opponent but for the most part it's a bug it ruined my record at top 5k .i was on a winning streak
I went from 30 stars to 11 stars cause of this and it all started after the content update from yesterday
