atp

He didn't say, but it was probably this:

https://mcpelauncher.readthedocs.io/en/latest/
https://github.com/minecraft-linux/mcpelauncher-manifest

Regarding Richard E Collard's update today, that, "Edit 5: Bug is still present, but I'm now very skeptical it's a Minecraft issue. I can't speak for everyone, but this seems to be an android issue."

I don't agree.  As I posted back on 2023-09-24, for us, the bug started IMMEDIATELY upon Minecraft upgrading to version 1.20.30, and the symptoms were identical on two different Android devices, a Google Pixel 6a running Android 13, and and a Google Pixel 3a running Android 12.  That sounds exactly like a bug in Minecraft, not in Android.

I have no idea how the Android controller APIs work.  Perhaps the bug boils down to using the APIs in a slightly wrong way, or failing to use a workaround for a known underlying bug.  If the Lego Fortnite developers have the same bug, that's interesting, but it could also just mean that they made the same mistake Mojang did.  To investigate it properly requires access to the game source code and version control history.  (E.g., "What controller-related code did we change in version 1.20.30?")

I also see no reason to make excuses for Mojang when they haven't even posted anything substantive to this thread.  If they actually investigated and discovered that the problem is due to an Android bug, they should say so here.  Since they haven't, probably they haven't.

Back in late October and early November, all Minecraft network play was still completely broken on my son's Google Pixel 6a, running Android 14.  I switched him to a DIFFERENT Google Pixel 6a that was still running Android 13 instead of 14, and he has stayed on 13 ever since.  That fixed everything, since then his Minecraft has been working normally.  It seems unlikely that the physically different phone mattered.  So probably Android 14 is necessary (although not sufficient) to trigger the problem.

On my son's Pixel 6a, re-installing Minecraft 1.20.40.01 (as I reported earlier) fixed local game play, but remote play with others is still completely broken.  Every time he tries to connect to a friend's device, his Minecraft app crashes.

Here's the crazy bit:  The bug appears to only affect HIS Pixel 6a.  I also have a Pixel 6a, and although I never play Minecraft, I do have it installed.  Minecraft on MY Pixel 6a appears to work fine, I can connect to/from friends' worlds just fine.  But on my son's Pixel 6a, it crashes every time.

We also recently installed the new Chromebook version of Minecraft, 1.20.40.01 running on ChromeOS 118.0.5993.86.  As far as we can tell it is fine, this bug does not appear there.

I concur with Iclarus, Minecraft 1.20.32.03 was very bad, but now with 1.20.40.01 it got WORSE.  When my son starts the Minecraft app on his Pixel 6a, the app IMMEDIATELY crashed, every single time!

First I uninstalled the app, while telling it to keep the data, and re-installed.  No change, the Minecraft app still crashed immediately every time we started it

Next I uninstalled Minecraft again.  This time it did not ask me whether I wanted to keep data; I think it deleted it.  I re-installed, and this time the app started without crashing.  His worlds were gone, but I manually installed them from a backup.  It SEEMS to be working correctly again now!  He hasn't actually used it much yet, so I don't know if they nasty crash bug will come back, but the re-install definitely seemed to help.

This sounds like the same problem my son is having.  He is also using a Google Pixel 6a, which upgraded itself to Android 14 sometime in the last week or two.  His Android Minecraft version is 1.20.32.03.

When he starts a local world on his phone, he usually can successfully load into the world, but it OFTEN crashes within the first 10 seconds of game play.

When he successfully starts his world, and then invites friends to connect, as soon as they try to connect, his world crashes!  As far as we can tell, EVERY time a friend tries to connect to one of his worlds, his world immediately crashes.  This happens both with the friend on the wifi LAN, and remote over the Internet.

When he tries to connect remotely to a friend's world, HIS local Minecraft client fails to connect every time.  The friend's remote world does NOT crash, and is seemingly fine.

Strangely, he seemingly CAN connect to and play normally on a Minecraft server version 1.20.32.03 running on Linux, on our LAN.

When his Minecraft world crashes, Minecraft exits the world WITHOUT saving, MOSTLY.  However, he sometimes sees weird glitches like this one:  At least once, he started a local world, spawned inside his house, took a shovel out of a chest, walked a short distance away, and then the world crashed.  When he re-started the world, he again spawned in the same location in his house as before - suggesting that no progress had been saved.  However, the shovel was MISSING from the chest, and completely missing from the world!  The shovel was NOT in his inventory, nor dropped anywhere else where his character had walked before the world crashed.  A strange bug, as if the crashed world did a PARTIAL save!

This buggy behavior started affecting him last night, Saturday 2023-10-22, and continues today.  Interestingly, it was NOT affecting him yesterday MORNING, but at that time, he was playing with NO network access at all (no wifi, no Internet).  Previous to that he had not played for a week or so.  Network access of friends trying to connect always triggers the world crash, so perhaps network access is implicated in general in some way.

Also, he often starts a Facebook Messenger Kids (similar to Skype) call on his phone and then leaves it running, in order to talk with his friends while playing Minecraft.  He has done that for years with no problem.  Today however, having the Messenger Kids call running in the background seemed to INCREASE the chance of his Minecraft world crashing.

These other two bug reports sound similar, although not exactly the same:

MCPE-172475
Blocks are placed more than once when you press the place button, and same with when breaking too.

MCPE-174864
Xbox LT Button not Working in Minecraft

We also have this exact same problem, which started when Minecraft upgraded to 1.20.30.  Symptoms are identical on two different Android devices, a Google Pixel 6a running Android 13, and and a Pixel 3a running Android 12.

We are using PowerA MOGA XP5-X Plus controllers with both phones.  The buggy behavior happens the same way when the controller is connected to the phone with Bluetooth, or with USB cable. Just like in the original bug report, if inside the Minecraft software we remap the place/break block functionality to a different button, the buggy behavior follows the physical button, NOT the place-block or break-block functionality.  We tried three different controllers (all the same model), and they all show the same buggy behavior.  And of course the original reporter is using a completely different controller (Razer Kishi V2), so the particular model of controller doesn't seem to matter.