I opened a few doors. When I reopen the world, the doors I just opened will shut.
@unknown added:
Steps to duplicate:
Doors
-Place a door on the ground.
-Open the door.
-Reopen your world.
The doors you just opened will shut. This affects all 6 door types.
See photos attached.
@unknown added:
This is no longer an issue for trap doors and gates. This is still happening with regular doors.
Linked issues
is duplicated by
relates to
Attachments
Comments


Affects 0.13.0 build 3

Yes it does

Affects 0.13.0 build 4.

Affects 0.13.0 build 5

Confirmed on Samsung Galaxy S4 Active Android 5.0.1 MCPE 0.13.0 build 5.

Confirmed on Samsung Galaxy Note 5. Android 5.1.1 Version: 0.13.0 Build 5
So annoying

Confirmed on devices: zte Blade g lux of android 4.4.2, tablet acer b1-720 of android 4.4.2, LG-50 Sporty 4.4.2, Huawey ascend Y300 of android 4.1.1. In 0.13.0

I have the same problem on the LG L90 Optimus

I am only just getting this issue after the update to v0.13.0 on the Windows 10 Beta.
Any trapdoors I created before the update now change to their closed position on entering the world.
Very annoying. I have had to resort to removing them.

Not only is it when the world is open, but when a new chunk is loaed in. This is what happens when a new team takes over for minecraft. They do not understand how the game is suppose to be played. This bug will probably be closed out as workes as intended.

This does not have to be a wall, but happens to trapdoors/fencegates anywhere, on any rotation as far as I can tell.

This happens to me too, it sucks because I used them for a mob grinder and now I have to go through the grinder to open all of them every time I go to get some XP.
A fix for this issue will be implemented in the future release. I am afraid that we do not have a date for this update at the moment. Please, do not report this issue for 0.13.0

Fixed in 0.13.1. Thanks.

It's back in 0.14.0... Yea....

Confirmed on Samsung Galaxy s4 Android 5.0.1 MCPE 0.14.0 build 1.

This issue affects doors in 0.14.0 build 4.

And this issue affects 0.14.0 beta build 7
Reported for test & fix.

Confirmed for 0.15.0 on Windows 10.
I assume this bug was wrongly associated with iron door bug and now it was reopened in internal bug tracker, for test and fix.

Confirmed for 0.15.90.2. (Tested on Pocket Edition.)
I have the same problem