cant open My world - running on android 4.4.2.

Similar, but crashes instead of error message

TCL 4035X, 4.4.2

I have the same problem on a new budget-brand tablet running MCPE 13.0 and Android 4.4.4 - it's a Spidotech Sleek W1:

http://spidotech.com/tablet.html

The error '"<World Name>" can't be opened' is seen every time i try to create a new world, even though the world is created on the SD card. I tried removing all of these created worlds and replacing with a known good world from a working Android tablet, but this one wouldn't open either. All other running apps have been closed. OS is up-to-date.

Please let me know what other information I can provide - I did check that the spec of this tablet meets the minimum spec for MCPE, so I don't think that should be an issue here.

n.b. I have posted on here because all other related reports seem to have been closed as 'Cannot reproduce'. The activity on the forum seems to indicate that this hasn't been resolved in the 13.0 update.

I have the same problem on a new budget-brand tablet running MCPE 13.0 and Android 4.4.4 - it's a Spidotech Sleek W1:

http://spidotech.com/tablet.html

The error '"<World Name>" can't be opened' is seen every time i try to create a new world, even though the world is created on the SD card. I tried removing all of these created worlds and replacing with a known good world from a working Android tablet, but this one wouldn't open either. All other running apps have been closed. OS is up-to-date.

Please let me know what other information I can provide - I did check that the spec of this tablet meets the minimum spec for MCPE, so I don't think that should be an issue here.

n.b. I have posted on here because all other related reports seem to have been closed as 'Cannot reproduce'. The activity on the forum seems to indicate that this hasn't been resolved in the 13.0 update.

so i bought MCPE v0.13.1 3 weeks ago for an android tablet and repeated attempts to use it have failed - ' "My World" can't be opened.'
i've spent 2 weeks trawling various forums, where i see this issue dating back to more than 1 year ago, to no avail.
it was only eur6.99 for me to purchase - no big deal. BUT the awesome gift of an android tablet for my daughter, with Minecraft installed, has turned out to be a big bummer.
can nobody help?

model number S102
android 4.4.4
kernel version 3.4.0+

so i bought MCPE v0.13.1 3 weeks ago for an android tablet and repeated attempts to use it have failed - ' "My World" can't be opened.'
i've spent 2 weeks trawling various forums, where i see this issue dating back to more than 1 year ago, to no avail.
it was only eur6.99 for me to purchase - no big deal. BUT the awesome gift of an android tablet for my daughter, with Minecraft installed, has turned out to be a big bummer.
can nobody help?

model number S102
android 4.4.4
kernel version 3.4.0+

If this issue is unassigned does that mean no-one is doing anything with it at all???

If this issue is unassigned does that mean no-one is doing anything with it at all???

I'm pretty sure the world is just corrupted. Idk if you can recover it because I don't have an android anything.

I'm pretty sure the world is just corrupted. Idk if you can recover it because I don't have an android anything.

@@unknown: we do not assign issues to specific developers.

So why do you have an assignee selection on the form above???

So why do you have an assignee selection on the form above???

Can anyone tell me in all honesty "is anyone actually working on this issue??"
Right now it feels like Mojang are saying "take a hike" (not my first choice of words!

!!
Regards,
Dave.

Can anyone tell me in all honesty "is anyone actually working on this issue??"
Right now it feels like Mojang are saying "take a hike" (not my first choice of words!

!!
Regards,
Dave.

"Unresolved"
Related issues marked as "Cannot Reproduce"

If you can't reproduce it, why not build us a special version with some debug logging in it? I'd happily run that and send the log back to you.
I'm a professional software developer. That's what I do when I work on an issue I can't reproduce.

"Unresolved"
Related issues marked as "Cannot Reproduce"

If you can't reproduce it, why not build us a special version with some debug logging in it? I'd happily run that and send the log back to you.
I'm a professional software developer. That's what I do when I work on an issue I can't reproduce.

@@unknown: this was a mistake. The related ticket should have been reopened immediately.

@@unknown: issues are typically only updated upon being resolved internally.

Does this issue still affects 0.14?, if so, please respond

Does this issue still affects 0.14?, if so, please respond

Just tried 0.14 on my son's tablet.

It still fails with the same message.

Is this a record for a bug? It's now been 15 months without a fix.

Just tried 0.14 on my son's tablet.

It still fails with the same message.

Is this a record for a bug? It's now been 15 months without a fix.

Yes it is still a problem, my kids are ready to bin their tablets claiming they are a waste of time since Minecraft does not work on them either that or find another cross device game for them & their friends to enjoy together!

Yes it is still a problem, my kids are ready to bin their tablets claiming they are a waste of time since Minecraft does not work on them either that or find another cross device game for them & their friends to enjoy together!

This is still a problem in 0.14.1 on iOS 9.3.1.

It may somehow be related to memory. It happens with worlds that have been played in a lot (11 MB or greater on my iPhone 6S, it seems), and reducing the render distance can help.

I can generate new worlds all day long. I have made hundreds trying for new seeds and never seen a crash with it. It's strictly limited to loading a saved world. When it crashes, it force-closes the app with no error message.

The world can eventually be loaded by restarting the app and trying again, but it can take several tries. Other times there is no problem at all.

I never play with other apps open in the background, so it's not that.

I'm not sure if this is the same crash others are experiencing. Please let me know if I should create a new issue or paste this comment on a different one.

This is still a problem in 0.14.1 on iOS 9.3.1.

It may somehow be related to memory. It happens with worlds that have been played in a lot (11 MB or greater on my iPhone 6S, it seems), and reducing the render distance can help.

I can generate new worlds all day long. I have made hundreds trying for new seeds and never seen a crash with it. It's strictly limited to loading a saved world. When it crashes, it force-closes the app with no error message.

The world can eventually be loaded by restarting the app and trying again, but it can take several tries. Other times there is no problem at all.

I never play with other apps open in the background, so it's not that.

I'm not sure if this is the same crash others are experiencing. Please let me know if I should create a new issue or paste this comment on a different one.

Random Brown - That looks like a different problem.

This issue is about not being able to create a world, but you say you can create them.
The program doesn't crash when we can't create the world - we just get an error message.

Raise a new issue.