1.18.30 - 1.19.20 is not compatible

[ratchild5]

1.18.3 on bedrock is not yet compatible for the launcher. it's a little annoying considering i can't play with friends on servers or on worlds, so hopefully its become compatible soon. sorry if i seem impatient !

[p0ryae]

You can still play in servers by using the last version, not the latest. 1.18.12 works very fine

[by5tark]

1.18.12 doesnt work more

[wertie3020]

the problem is android and windows auto update so all servers have to update to the latest version as fast as poseble becos atherwise they lose players

[CapLifter]

When will this be fixed?

[wertie3020]

i don't know but i hope soon

[RedsonBr140]

@ChristopherHX what about?

[t1mest0ne]

does anyone know if or when the latest version is going to be compatible with the launcher?

[RedsonBr140]

I think you can close it now

[ChristopherHX]

The 1.19, could be closed, because it is technically a duplicate of this one

1.18.30-1.19.21 is available for testing on flathub beta ( linux arm64 and amd64 devices ).
Known Issues

• The qt UI suggests to install the armeabi-v7 version of the game, while it shouldn't offer it on amd64 devices
  • Workaround 1: this workaround works as long 1.19.21 is the latest version of the game
    • Open Settings
    • Switch to the Dev Tab
    • Enable Show Unverifed versions
    • Now you can download and play 1.19.21
  • Workaround 2: to be documented
    • edit the profiles file and replace the versions code of an existing profile to 1.19.21 see https://github.com/minecraft-linux/mcpelauncher-versiondb/blob/master/versions.json
• Xbox Live Sign in is broken in the beta
  • you need to sign in with Minecraft 1.18.12 via the normal flatpak version
• Some Devices may freeze within a minute, you might be able to load a world and play for 5-10s
  • No workaround, backup your worlds before upgrading or they are lost in 1.18.12
• 1.19.30 is not compatible

[ktheticdev]

Even if I sign in in 1.18.12, 1.19.22 says that "there was a problem when signing in" (same with 1.18.12, btw, but here I can at least click "sign in" again), so I am unable to use Xbox Live. What could be the problem?

[ChristopherHX]

What could be the problem?

You pressing the sign in button, before auto sign in completes.
If you signed in successfully in 1.18.12, you just have to wait until the sign in button disappears in 1.19.21.
Otherwise someone can contribute to the xbox sign in logic of this launcher to improve it. As long it works for me nothing needs to be improved from my side.

[ktheticdev]

What could be the problem?

You pressing the sign in button, before auto sign in completes. If you signed in successfully in 1.18.12, you just have to wait until the sign in button disappears in 1.19.21. Otherwise someone can contribute to the xbox sign in logic of this launcher to improve it. As long it works for me nothing needs to be improved from my side.

From what I've seen, it basically hangs and GNOME states that it's not responding.

[awuioebhjnd]

I cant find 1.19.21 only 1.19.20.24 which is locked even on the dev unverified version and on the flat hub one. anyone know what im doing wrong?

[ChristopherHX]

From what I've seen, it basically hangs and GNOME states that it's not responding.

If you mean the launcher with the title Minecraft, it is the known issue "Some Devices may freeze within a minute, you might be able to load a world and play for 5-10s".

No clue what happens, running the same code outside of the flatpak sandbox kept responding on my device.
My other device didn't have this problem at all.

I cant find 1.19.21 only 1.19.20.24 which is locked

Sounds like you downloaded a pirated old beta version of the game, otherwise I have no idea why you even have that beta of the game. Beta versions are locked behind another toggle.

[ChristopherHX]

Closed via 4c7dadf