This issue is detrimental to many addons even for the marketplace since custom items are now out of experimental. It makes all forms of custom stuff that involve "eating item" as a workaround not work properly on multiplayer. This is a big issue that is likely rather easy to fix and yet has not been done for such a long time.
Mojang pls fix
This issue also happens on custom entities. I'm not sure how to describe it but it also sometimes happens when standing on barrier blocks (in a certain angle)
Alexa is right. It is a network problem. I changed the wifi i was connected to and then Minecraft loaded again. Even if i use the old one it still works now but sometimes it happens again and the solution is still the same thing.
@CJC
I didn't think about using ^ after execute instead of ~. I'll see if there's a difference,thx. As for the armour stand killing when ur nearby thing, I prefer just having an invisible armour stand there. But for now all my armour stands are now visible until this bug is fixed.
@CJC
For example, an armour stand is renamed Look1
/execute @p ~ ~ ~ tp @e[name=Look1] ^ ^ ^+4
This teleports the armour stand 4 blocks in front of whereever you look at. Problem is, you might put ur item onto this armour stand and it disappears. It's very hard to retrieve
CJC On my map I'm trying to detect looking at an entity. So I teleport an armour stand in front of you relative to wherever you are looking and run a testfor. Problem is if you accidentally place an item on the armour stand it disappears and is very hard to find again.
@Sam Bushell
Yup I changed wifi network and minecraft works again. This is still a major issue though
Check MCPE-45437 for reference on my encounter with this issue.
Reinstalling the game didn't do anything
It happens on iPad too, on 1.10. If there are other armour stands nearby the invisible one. The item the invisible armour stand is holding will appear on them, although it isn’t actually there. This glitch is quite annoying for map making.
[media]If "platform" says none. It should be iOS 12.11
I searched it but I didn't find the same thing
We're still waiting... Detrimental issue that doesnt get fixed