Earl Borah

This was an issue for several betas (through 1.16.0.64), but appears to be resolved in 1.16.0.66, as best I can tell.

DenixCo - not even close. The "Marketplace" crash happened on startup of the game when it auto-checks the marketplace if you own content, making it completely unplayable on Android AND on some Windows 10 devices (including mine). I hadn't been able to play for a week, while my wife on our XBox could play but was unable to smith gold or benefit from fortune-enhanced tools. No contest - the bug that makes the game 100% unplayable is worse than the one that inconveniences one aspect of gameplay. If you're desperate, swap to creative, throw your ore into lava and replace it with ingots, and swap back.

Reese: Not that hard to believe. I haven't been able to play for a week, as the last beta broke Minecraft so bad the game wouldn't start on my Windows 10 or Android devices. If they prioritized fixing that over fixing gold smithing or fortune working, then I applaud them. If the beta is a problem, you can always quit the beta and go back to a release version where fortune works.

I have the same issue on Windows 10 - XBox One S works fine. The prior beta (.55) worked fine, despite some bugs.

See also, MCPE-69009 and MCPE-68984 and others, none of which seem to be acknowledged yet.

I am also having this issue with beta 1.16.0.57 on Windows 10, but not on the previous beta (1.16.0.55), and not on XBox One S.

The game closes without any error message seconds after showing the main menu, usually before I have a chance to select anything. I am using a custom skin and a non-default Resource Pack (Chroma Hills) on the Windows 10 machine as the default - the XBox One S uses Chroma Hills as well, but only loads it when it loads a  world  - I can't get in long enough on the Windows 10 machine to change settings to see if that makes any difference.

See also MCPE-68984, probably others.

Confirmed, this appears to be fixed in beta 1.16.0.53. THANKS!

My wife and I each see this on our accounts on both Windows 10 and XBox, ever since the 1.14.1.3 beta.

My phone did not initially have the same issue, even though it's on the same beta version. Then I "bought" the free bees-themed world you released today - the purchase worked, though it did not appear to download. Now I get the same error on my phone as well.

See also MCPE-59355 which looks like it might be a duplicate of this issue.

On 1.13.0.2 now, and this seems to work - only one village checked so far, but villagers who were "out" and hadn't been willing to trade for a week suddenly started trading again.

See also, comment on MCPE-46062 posted 8 hours before this issue was created, same issue (different ticket).

I play on XBox One S and Windows 10 (multiplayer over LAN, typically hosted on Windows 10) - issue appears consistent.

I'm seeing the same thing as Ben - no matter how long I stay in a village (several consecutive nights), the villagers don't seem to get more inventory to trade any more - once they're out, they're out, seemingly forever, in build 1.13.x.

I assume that will need to be a new issue. I looked but didn't see an issue like this posted yet, so I made MCPE-48319

I'm on 1.12.0.11, and haven't had this problem for the last several betas. I used to, but it stopped at least three releases back, maybe more. I tested last night to confirm - trades happening as expected, and I'm getting what I'm trading for.

Using a controller on both Windows 10 and XBox One.

I did have a similar issue on a prior beta (comment above mentions 1.7.0 and 1.7.1), but not for a while. We do play with the City texture pack enabled. I haven't yet tried it without a texture pack enabled - I'll do that and update the comment.

I was able to start a new world on the PC and have the XBox One connect to it, but the other direction still doesn't work (still on Bedrock beta 1.9.0.0).

My wife and I play on a LAN (she on an XBox One S, I on a Windows 10 laptop with more RAM, NVidia video). We've noticed this a lot, but only since the 1.6.0.8 build. The non-host can continue to play for about 10-30 seconds after the primary freezes (or, when hosted on the PC, quits suddenly) before getting a message the server has been lost.

We've used a UI theme (PureBDcraft UI, with city texture) when hosted on XBox that shows an icon when autosave kicks in, and noticed when the crash happens, it seems to happen at the same time as an autosave. That seems VERY consistent on the XBox - not sure when it's hosted on the PC, as that account doesn't own the same theme (city texture active, but PureDBcraft UI not owned/enabled) and instead of freezing, Minecraft on the PC just quit and dropped me to the desktop.

I'm not convinced it always happens with the speed of a player (as some of these reports suggest), as most recently it happened in a new world hosted on the laptop (we usually host from the XBox), where we were playing in survival and did not yet have horses tamed, or boats built.

I did lose a horse I was riding one of the times it happened, however, so that element seems somewhat consistent.

This might be the same bug as MCPE-36270, which also mentions the link to autoasave.