Affected platforms: Amazon, Android
any time you try and play minecraft since update 1.16.20 if you have no internet the game crashes randomly i have tried on my All new amazon fire 10 and on my brothers All new amazon fire 10 both are quite new mine being less than half a year old and the game crashes randomly whether it may be on the main screen or in a world the game crashes it never did this in 1.16.10
Linked issues
is duplicated by
Attachments
Comments


Same issue here. I think the game doesn't realize it's offline, and keeps trying to sign in to Xbox. Somewhere in this process it crashes. But if you turn off your Wi-Fi after you're signed in, it works fine.

Same issue here. I think the game doesn't realize it's offline, and keeps trying to sign in to Xbox. Somewhere in this process it crashes. But if you turn off your Wi-Fi after you're signed in, it works fine.

@Dragonairre Gaming yep, but when I tried to open Minecraft with my data connection on, but when I turn off, it crashes.

@Dragonairre Gaming yep, but when I tried to open Minecraft with my data connection on, but when I turn off, it crashes.
@unknown That issue is specifically for iOS devices and did not appear in 1.16.20, whereas this is for Amazon/Android devices and only for 1.16.20 and above.
@unknown That issue is specifically for iOS devices and did not appear in 1.16.20, whereas this is for Amazon/Android devices and only for 1.16.20 and above.

Oh, okay. This must relate to that issue then. They sounded the same from the descriptions.

Oh, okay. This must relate to that issue then. They sounded the same from the descriptions.

I’m having the same problem too. iPad mini 4

I’m having the same problem too. iPad mini 4

Can confirm. On iOS, opening the game without internet crashes on load. Makes traveling a pain.

Can confirm. On iOS, opening the game without internet crashes on load. Makes traveling a pain.

Can confirm. Only affects me when I am signed into a Microsoft account. The easiest way to play offline is to connect to a hotspot or wifi, sign out of the account, and sign back in later when you are done playing offline. Affects iOS 13.6.1 on iPad

Can confirm. Only affects me when I am signed into a Microsoft account. The easiest way to play offline is to connect to a hotspot or wifi, sign out of the account, and sign back in later when you are done playing offline. Affects iOS 13.6.1 on iPad

Same here.

Same here.

Reporting that the error still persists even with the update of 1.16.40; it keeps giving the same error

Reporting that the error still persists even with the update of 1.16.40; it keeps giving the same error

I'm on kindle fire and still have the issue... When will it get fixed?

I'm on kindle fire and still have the issue... When will it get fixed?

Its still here even after the hotfix. ( 1.16.40)

Its still here even after the hotfix. ( 1.16.40)

Will voting for it help it get fixed faster?

Will voting for it help it get fixed faster?

la version 1.16.40 genero muchos problemas en android s7 edge samsung al hacer clic en iniciar secion quiere conectarse a microsoft y se cierra la app no se puede ingresar con tu perfil

la version 1.16.40 genero muchos problemas en android s7 edge samsung al hacer clic en iniciar secion quiere conectarse a microsoft y se cierra la app no se puede ingresar con tu perfil

@Elijah Vogler The more votes there are on an issue, the more Mojang will think it needs to be fixed.

@Elijah Vogler The more votes there are on an issue, the more Mojang will think it needs to be fixed.

This happens when disabling WiFi

This happens when disabling WiFi

For me it just happens when I'm signed into my microsoft account. If I'm not signed in I can play offline tho

For me it just happens when I'm signed into my microsoft account. If I'm not signed in I can play offline tho

Why was this added as a version to the issue tracker?
[media]

Why was this added as a version to the issue tracker?
[media]
This bug is fixed in the latest beta version, and the fix will be included in a future update when that is ready for full release (no specific date can be given). We will leave this ticket open as a point of reference until the fix has been fully released.
This bug is fixed in the latest beta version, and the fix will be included in a future update when that is ready for full release (no specific date can be given). We will leave this ticket open as a point of reference until the fix has been fully released.