[MCPE-4212] Multiplayer via WIFI crashes Created: 11/Jun/13  Updated: 07/May/15  Resolved: 17/Jul/14

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.7.0, 0.7.1
Fix Version/s: None

Type: Bug
Reporter: I sim
Resolution: Cannot Reproduce Votes: 1
Labels: crash, multiplayer, wifi

Game Mode: Survival
Confirmation Status: Unconfirmed
Platform: Tablet - Android - Other (Specify in description)

 Description   

Random crash happens every time I am playing on wifi. My kid and I both have nextbook 7" tablets, 1ghz processor w/ 8gb internal memory, 1gb ddr, and android 4.0

I can play single player all day long with no crash.. Its when we are playing together that the game freezes and gives me the "game is not responding" menu with the choice to ignore or quit.

Too lame for words, please fix this. I never had a problem with 0.6.1

Is there a way I can roll back the updates to 0.6.1, i am tired of not being able to use this game

Thanks



 Comments   
Comment by tommo [ 17/Jul/14 ]

Cleaning up old issues, please reply if affecting 0.9.3

Comment by Jason Woods [ 24/Jun/13 ]

I commented on another similar. I have the same issue.

Single player is fine on 0.7.1. Multiplayer survival crashes with new maps, same M.O. as yours, freezes and get "wait, ok" menu. My old map seems to work fine, as does single player creative. Though it could be that it is so random that we didn't play long enough for a crash.

Two nook colors, Cyanogenmod 10.1, stock Samsung S3, Samsung Galaxy Nexus CM 10.1.

Comment by I sim [ 24/Jun/13 ]

nah, i am running new maps as well and it still crashes. The hosting tablet will become laggy while serving the map, and eventually succumbs to the lag and crashes. we've done this on both tablets, so its definitely a game-related crash.

Comment by I sim [ 12/Jun/13 ]
    • this was on a map i created during 0.6.1.

I think there are some backward compatibility issues among your updates

after update, i guess ill just have to wipe my previous games

Generated at Sat Jan 11 14:24:18 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.