This links to JAVA indeed, thank you, this platform is like a never-ending hole to find something!!! All I know is that i am on Bedrock version 1.20.41 and my ESC key does not pause the game and it has been an issue for the last couple of updates... 

I am on 1.20.41 and it doesn't work for me.

 I have to spam hit the ESC key if i want the exit menu to appear. Single player. Realms and Server. (Bedrock V.1.20.32)

This is forsure still a thing✔ ! Used up a lot of bonemeal, but nothing. 😉 Hope the next update fixes this... Thanks.🙂

I was so hopeful that 1.18 would bring a fix to this issue... but alas, not yet... we still have to use the /me 

I know of many realm owners who are having these errors.

This is still happening!! I thought it was reopened and being looked into?

Steps to Reproduce:

1. Join realm.

2. Play on realm and interact with online friends.

3. Chat in game with them.

4. After a few exchanges ... chat goes silent and messages do not go through. 

5. Then randomly, all the past chats will pop up all at once.

Observed Results:

As discussed above, the chat becomes unresponsive mid playing. It seems ad hoc, rather that at specific times. This is for ALL players online. In game /msg chats will sometimes go through even if you use @a or target a specific player. Regular messages DO NOT go through during this time at all.

Expected Results:

In-game chat needs to go through without a delay and players should not have to use /msg to contact players. Chat should not be delayed for all players, and pop through all at once and spam the chat.

(Also you ticket link for an example leads to a page that does not exist.)

Whooo!!!! Thank you so much!!

I have Foxy's  Single Player Sleep, and Mob Heads packs enabled. I also have DanRobProz's Armor Stands and Slack Lizards' Particle pack. Suddenly, we have so many custom recipes available in survival now - i.e. mob spawner; mob eggs; elytra; etc. I am fortunate to have really good players in my realm, who will not take advantage of this, however this bug needs to be fixed please. The report is 100% accurate.

How did you change the UUID?

I have a 5 x 5 grid of torches around my base. Before the update I had no mobs spawning due to the acceptable light levels, however in 1.16 mobs, especially creepers, spawn randomly. One even spawned right next to a torch. There was no time to screenshot! The rate of creepers spawning is also extremely overwhelming! In my realm we play on "normal" setting, but these days I turned it to "easy"... even now still, the creeper spawn rate on easy, is just too high. 

I own a realm, and the creeper spawn rate on EASY is through the roof! I went to hunt Stray's in an ice biome, and creepers kept spawning. I have a 5 x 5 torch grid around my base, and have never had creeper i(or other mob) issues, but now all of a sudden, creepers spawn around my base area...

And out of the blue, it is back. Some areas just don't load in on our realm. And what is funny is, that some players can see all the blocks and for other's it is just gone. I actually fell into a chunk, but could not place blocks to get out. When i tried placing blocks, the blocks that were there  re-appeared: one by one. Other players int he realm is not as fortunate, with whole chunks not loading. It is not just momentary glitches, it either requires a whole realm reset, or an xbox hard reset... simply closing and re-opening the game does not work either.

We have been experiencing a lot of lag in our realm recently, and I suspect this might be the cause... Yesterday I killed 23 Ghasts just over this small area. (See photo)... this was not even all of them. 

Same here... So frustrating.

Also happening in v.1.13.1

This bug is so ridiculous... many of my realm players are refusing to play until it is fixed, because they have lost all of their gear!!! So dumb.

We are also having this issue (again)... We had it earlier this year, but as reported, it seemed to fix itself. Now it is back again, and it is the exact same chunk which did not work before and people keep getting stuck (as reported by everyone above). I agree with Nicolas, "the bug is somewhere between really annoying and critical!"