ktorn

This issue affected me, as I was trying to setup an AFK account on a Bedrock Realm.

In order to have the account active 24/7 I created a Windows VM on a headless home server to run the Minecraft client.

It works as long as I keep a Remote Desktop connection actively connected to the VM, keeping the Minecraft client in focus, but as soon as I disconnect the Remote Desktop session then the Minecraft client also disconnects from the Realm.

My own workaround was to create a second VM on the same server, with Ubuntu Linux, from which I establish the Remote Desktop connection to the Windows VM. I can close any remote connections to Ubuntu because it still keeps the RDP connection to Windows active, therefore keeping the AFK account always connected.

If I'd known about this issue in advance I'd have tried to simply run Minecraft on an Android emulator directly on a Ubuntu VM, but my current setup works.

After looking at MCPE-159616, we did a few more tests on our realm.

Our findings:

• The allay only starts ignoring leads the moment the player who last attached a lead to that allay goes through a nether portal, including if the allay was attached to a fence post by that player.

• This means other players who did not interact with the allay can go through nether portals without affecting it.

• When an allay starts ignoring leads then all players who are currently logged into the realm need to exit and re-enter the realm to restore that allay's normal behaviour.

Also having a similar issue in a multiplayer bedrock realm.

3 players rescued 4 allays from an outpost. They all responded well to leads all the way to the nether portal. Once in the nether, we could still visibly attach leads but they no longer followed us and the leads just kept breaking. I should note that one of the players did report some success with their lead allay. 2 of us had to resort to continuous dropping blocks for the allays to follow us back to base. (note: we were just walking, not running, flying, nor using boats on ice)

Most surprisingly, once back in the overworld, they allays still don't respond to leads. Even when attached to a wooden fence, they simply wander off until the lead breaks off the fence. We all had to build full enclosures to keep them from wandering off.

I also confirm issue sorted after Nether update on PS4.

Issue fixed with Nether update.

@IonicEcko, I'm having the same issue, and yes it is error -9.

This is a new error that is now appearing, after over 3 weeks of simply not being able to login at all (see MCPE-58464) for which I opened a private ticket as instructed (see MCPE-77896).