Volodymyr Grynchyshyn
- tomdill
- JIRAUSER557446
- Europe/Kiev
- Yes
- No
MCPE-102152
My Minecraft on my phone currently crashes as soon as it starts to sign in to Xbox Live. It even does not open a Chrome browser window to sign in or confirm it. I tried to clean up the app cache, sign in data in Minecraft profile, clean up the phone system cache, and completely uninstall and install back the Minecraft itself. None helped. When I installed Minecraft back, I found out that some worlds are back there and some settings as well, which means reinstalling does not clean up all the data on the phone. And I really really do not want to reset the phone to factory settings that will wipe out everything.
So, this issue is: make the sign-in process more reliable. Alternatively, provide some way to completely wipe out all the data associated with Xbox Live account and Minecraft on the phone to start anew and be able to sign in after reinstall.
What happened:
I temporarily installed Minecraft under Bluestacks on MacOs to try few things (include performance) and logged in to Xbox Live there. After that, I found out that my Minecraft on my phone where I play most of the time automatically signed out. It's ok, but, after that, sign in stopped to work.
I read a lot of articles and support info, but did not find any good solution to my problem. I also wrote to Mojang support (request 1200133), but the answer was only "Unfortunately, we are not able to provide further support in this matter due to differences with individual computers, and our support is limited mostly to accounts and billing." I also had a chat with Xbox Live personnel, but they said they even do not have any ways to help me to wipe out data related to Minecraft-XboxLive communication during the sign-in process. So I create this ticket in a hope that devs can help to fix this problem.
Details about my setup:
- Phone is ASUS_Z01KDA, Android version 8.0.0
- Xbox Live account: TomDill2883
- MS account user: tomdill
- First bought Minecraft for Xbox 360 on the Xbox Live and played there for some time
- Installed Minecraft on the phone and signed in to Xbox Live in version 1.16.0, after that sign-in worked automatically (until this issue)
- Storage was "Application" only. (Switching storage to External does not fix the issue.)
- Had achievements unlocked, character skin modified (with items I get from unlocked achievements)
- I downloaded from the Minecraft marketplace only Minecraft's original music soundtracks package (the free one).
Steps to reproduce:
- Played for a long time on the phone with the above setup, mainly in the survival mode. Some worlds are already 128MB+ size
- Installed Minecraft on the BlueStacks for MacOs (Android platform that runs on PC) and signed in to Xbox Live there
- played there a bit, changed some settings, include changed storage to External
- opened Minecraft on the phone and found out it's no longer signed in automatically to Xbox Live account
- Tried to sign in and the game crashed
- cleaned caches, including system cache, after phone restarts, etc. Tried to sign in again and failed.
- uninstall Minecraft and install it from Play Store again. Discover some very old worlds (existed prior to the first SIgn in) are still displayed and playable after the first run after reinstall. Possibly some corrupted data are also left because I still could not sign in.
Expected behavior:
- Sign in works in a more reliable way
- Uninstall and install of Minecraft cleans up data on the phone completely to allow sign-in anew as if during the first install on that phone. Alternatively, provide a tool to completely wipe out all Minecraft-related data on the phone to allow start anew.
My Minecraft on my phone currently crashes as soon as it starts to sign in to Xbox Live. It even does not open a Chrome browser window to sign in or confirm it. I tried to clean up the app cache, sign in data in Minecraft profile, clean up the phone system cache, and completely uninstall and install back the Minecraft itself. None helped. When I installed Minecraft back, I found out that some worlds are back there and some settings as well, which means reinstalling does not clean up all the data on the phone. And I really really do not want to reset the phone to factory settings that will wipe out everything.
So, this issue is: make the sign-in process more reliable. Alternatively, provide some way to completely wipe out all the data associated with Xbox Live account and Minecraft on the phone to start anew and be able to sign in after reinstall.
What happened:
I temporarily installed Minecraft under Bluestacks on MacOs to try few things (include performance) and logged in to Xbox Live there. After that, I found out that my Minecraft on my phone where I play most of the time automatically signed out. It's ok, but, after that, sign in stopped to work.
I read a lot of articles and support info, but did not find any good solution to my problem. I also wrote to Mojang support (request 1200133), but the answer was only "Unfortunately, we are not able to provide further support in this matter due to differences with individual computers, and our support is limited mostly to accounts and billing." I also had a chat with Xbox Live personnel, but they said they even do not have any ways to help me to wipe out data related to Minecraft-XboxLive communication during the sign-in process. So I create this ticket in a hope that devs can help to fix this problem.
Details about my setup:
- Phone is ASUS_Z01KDA, Android version 8.0.0
- Xbox Live account: TomDill2883
- MS account user: tomdill
- First bought Minecraft for Xbox 360 on the Xbox Live and played there for some time
- Installed Minecraft on the phone from Play Market and signed in to Xbox Live in version 1.16.0, after that sign-in worked automatically (until this issue)
- Storage was "Application" only. (Switching storage to External does not fix the issue.)
- Had achievements unlocked, character skin modified (with items I get from unlocked achievements)
- I downloaded from the Minecraft marketplace only Minecraft's original music soundtracks package (the free one).
Steps to reproduce:
- Played for a long time on the phone with the above setup, mainly in the survival mode. Some worlds are already 128MB+ size
- Installed Minecraft on the BlueStacks for MacOs (Android platform that runs on PC) and signed in to Xbox Live there
- played there a bit, changed some settings, include changed storage to External
- opened Minecraft on the phone and found out it's no longer signed in automatically to Xbox Live account
- Tried to sign in and the game crashed
- cleaned caches, including system cache, after phone restarts, etc. Tried to sign in again and failed.
- uninstall Minecraft and install it from Play Store again. Discover some very old worlds (existed prior to the first SIgn in) are still displayed and playable after the first run after reinstall. Possibly some corrupted data are also left because I still could not sign in.
Expected behavior:
- Sign in works in a more reliable way
- Uninstall and install of Minecraft cleans up data on the phone completely to allow sign-in anew as if during the first install on that phone. Alternatively, provide a tool to completely wipe out all Minecraft-related data on the phone to allow start anew.
Llamas left after mob kill trader (don't despawn)
@Adonis Taruc, if you know a workaround please, share it. Many ppl suffer from this.
One more case: Finally found a cave where Llama sounds below my base were for so long. And the killer was a baby zombie. See screens
@Håkan, It's most likely an app issue as I see on Stack Overflow:
https://stackoverflow.com/questions/58990214/application-not-working-in-some-device-like-samsung-galaxy-j7
Though I may be wrong. The actual error is "Only fullscreen opaque activities can request orientation", which means, activity launching fails for other reasons, not because of WebView or related updates.
I wonder, what is the status of this issue? Many ppl experience it and yet no official answer that this will be fixed?
Somehow, it worked in prev versions of Minecraft? I do not think it's an Android version issue, therefore.
I have an option to upgrade my Asus to the beta Android 9 without any support only. And I'm almost sure many ppl cannot upgrade at all (upgrading the phone to another major Android version is always a big issue for many phone manufacturers).
So I beg you just fix this issue.
It's really really hard to switch storage with preserving all the worlds. It made me nuts and guts until I found a solution to copy the world from internal storage to outside when I tried to reinstall, and I'm a developer - what to tell about regular users? You can root device, but it costs either money or time and effort nearly the same as just make a copy. And complete application backup with data does not work for Android 8, so most users are still trapped here unless they are easy with losing all the worlds during reinstalls.
Conclusion: all workarounds I know are really hard, nearly impossible for regular users. So this issue remains a blocker for many players.
@JuanCarlos Aguilera, please, read my comment. When you uninstall MC, all worlds are lost if storage was application internal. And, @AM71113363, when you switch to external, worlds do not copy and are still lost when you uninstall MC, and you cannot just copy them that easily. So, that approach with "Toolbox for Minecraft: PE" will work for new MC users only (or users who already set to store worlds externally, that is NOT default). For existing users that play for a long time reinstalling Minecraft (even to an older version) is not an option at all, so it's still a significant blocker issue for a large number of users.
TO use Realms, you need to sign in. And we cannot
"Minecraft Pocket Edition World Exporter" is exactly the way I did copy my worlds manually without a tool, just from the command line. Still troublesome, not all have Windows at hand (I did it from Mac OS).
Confirming it works now. Doh, so many achievements not recorded (( And had to redo my character design completely as it's lost.
Please, make sure it is fixed in all places for all packets. For example, I'm getting also the same issue with "ClientboundBlockChangedAckPacket".