Not resolved yet!
To Android players:
You don't have to understand the content below the horizontal ruler, but I'm also glad if you understand.
A file migration might happen on your Android device later if your "File Storage Location" is "External".
Pay attention to the official announcement about this incoming migration. You might be advised to backup something.
If beta on your Android 11 device is not working properly anymore, backup your files and set "File Storage Location" to "Application" temporarily. If beta seems still working correctly on your Android 11 device, don't re-install your beta version of Minecraft.
To developers:
Meet Google Play's target API level requirement
Google Play's target API level requirement
Starting in November 2021, app updates will be required to target API level 30 or above and adjust for behavioral changes in Android 11.
I know this isn't a typical bug. This is a technical issue with a potential privacy issue. I will give my resolution. Considering this suggestion will be outdated after November, I've decided to post it here.
Not that all of players on the Feedback website know about app development. I don't expect players to vote for a suggestion they don‘t even understand.
Without enough votes, it's impossible for this suggestion to be watched by the developers before November.
The Play Store is starting to require app updates to target Android 11 in November.
Starting in November, updates of Minecraft have to target API level 30 or the Play Store will not accept.
To readers don't know about API level: If apps target to a new API level, they have to behave as if they are installed on the correct Android version, regardless of the current Android version the user is using.
The behavior changes of Android 11 include the scoped storage enforcement. Storage updates in Android 11
Scoped storage enforcement
Access into external storage directories is limited to an app-specific directory.
Obviously, the directory "/sdcard/games" that Minecraft uses when "File Storage Location" is "External" is beyond the app-specific directory of Minecraft. Minecraft that targets API level 30 is losing the permissions for that directory, which could result in disappearance of currently imported worlds, resource packs and behavior packs and disability to create any world, which has happened in 1.17.30.20 Beta on my Android 11 device!
MCPE-137652
Of course, apps that target API level 30 can still ask for read and write permissions for any specific directory using the SAF Picker. However, on various modified Android OSs, the Picker doesn't always work. For example, on MIUI, the Picker doesn't have full privileges, which is different from other AOSP powered OSs. There are many other disadvantages, but I don't want to go into details. It can only be a plan B.
Q. E. D.
My resolution:
Minecraft on Android is supposed to migrate files to a new directory inside of "/sdcard/Android/data/com.mojang.minecraftpe"(the correct directory for "external files" on Android 11).
Steps:
Release a new version that targets API level 29. Let players do not uninstall before step 2. In this version, migration is not necessary but recommended. With android:requestLegacyExternalStorage="true", Minecraft can get the permission for the file migration.
Release a new version that targets API level 30. With android:preserveLegacyExternalStorage="true", Minecraft can keep the permission for the file migration temporarily. Migration must be done.
Repeat step 1 and step 2. If the player has still skipped step 1, Minecraft doesn't have the permission at this stage. Try asking for the permission using the SAF Picker.
Note that the destination is private on Android 11. Files will be migrated from a public directory to a private directory. It will be a bit difficult for players to access their worlds, resource packs and behavior packs in the filesystem directly after the migration.
Precautions:
Have migration tested in beta before adding it into release.
Inform Android players of the full details of the incoming migration as soon. Players have the right to get informed.
The old directory is "/sdcard/games/com.mojang". Minecraft is supposed to migrate the "com.mojang" folder only, because there could be other app(s) still using the "games" folder. Only when the folder is empty, Minecraft will be supposed to delete it.
The new directory will be deleted when uninstalling.
Any first install of Minecraft could be a re-install.
Considering the new directory is private, an "Export World" button should be provided to players, and add-on developers affected need new FAQs.
Linked issues
relates to 1
Attachments
Comments 23
Thank you for your report!
However, this issue is Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit Minecraft Suggestions on Reddit or visit the Feedback website.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
However, this issue is Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit Minecraft Suggestions on Reddit or visit the Feedback website.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Please, let the dev team take a look. I know this is a suggestion.
But not that all of players on the Feedback website know about app development. You can not expect players to vote for a suggestion they don‘t even understand.
Without enough votes, it's impossible for this suggestion to be watched by the developers before November.
@Umija5895
Please, let the dev team take a look. I know this is a suggestion.
But not that all of players on the Feedback website know about app development. You can not expect players to vote for a suggestion they don‘t even understand.
Without enough votes, it's impossible for this suggestion to be watched by the developers before November.
@Umija5895
Although it looks like we just invalidated this report and ignored it, we didn't and it has now had the effect you intended. Invalidating it was the appropriate action we had to take because the bug tracker isn't designed for communicating "future bug" information like this. (I'm not sure what is, probably the Feedback site or perhaps the Minecraft Discord?) But we were keeping track of it to pass it on, and the delay was due to timing: On the day you submitted this, the person we needed to pass it to wasn't available, and since then it was the weekend.
Rest assured, this issue is now being tracked internally by Mojang. It is, in fact, already causing problems for some people using Android 11 external storage, and you might like to follow MCPE-137652 for developments.
Although it looks like we just invalidated this report and ignored it, we didn't and it has now had the effect you intended. Invalidating it was the appropriate action we had to take because the bug tracker isn't designed for communicating "future bug" information like this. (I'm not sure what is, probably the Feedback site or perhaps the Minecraft Discord?) But we were keeping track of it to pass it on, and the delay was due to timing: On the day you submitted this, the person we needed to pass it to wasn't available, and since then it was the weekend.
Rest assured, this issue is now being tracked internally by Mojang. It is, in fact, already causing problems for some people using Android 11 external storage, and you might like to follow MCPE-137652 for developments.
/sdcard/Android/Media/com.mojang.minecraftpe is correct than that one
/sdcard/Android/Media/com.mojang.minecraftpe is correct than that one
@unknown: The directory "Android/media" has been deprecated. Don't use it. Although (as a app-specific directory) access into existing one is still allowed, without extra permission, Minecraft that targets API level 30 can't create "Android/media/com.mojang.minecraftpe" anymore.
@unknown: The directory "Android/media" has been deprecated. Don't use it. Although (as a app-specific directory) access into existing one is still allowed, without extra permission, Minecraft that targets API level 30 can't create "Android/media/com.mojang.minecraftpe" anymore.
The bug (in MCPE-137652) was fixed in the latest Beta release. There should no longer be any reason to update this ticket.
The bug (in MCPE-137652) was fixed in the latest Beta release. There should no longer be any reason to update this ticket.
@unknown: That's fake. The reason why the bug doesn't cause any problem in v1.17.30.21 beta is that this version targets API level 29. We're at step 1 that hasn't added the migration. It's not over.
@unknown: That's fake. The reason why the bug doesn't cause any problem in v1.17.30.21 beta is that this version targets API level 29. We're at step 1 that hasn't added the migration. It's not over.
If, as you say, it "doesn't cause a problem" then it isn't a bug. There apparently was a bug, but it wasn't tracked on this ticket and besides, the bug has been fixed now.
The problem you're referring to now is a potential bug which could theoretically become actual, if the developers inexplicably fail to prevent it despite advance notice. But as I said before, the bug tracker is not intended for speculating about future bugs. Therefore this ticket is not being used to track anything.
(If you don't know, the Bedrock developers use an internal tracking system to manage issues and generally aren't aware of updated information on Mojira unless the mods direct their attention to it. I'm told they have a ticket in their system for this upcoming change for Android 11, but they originated it internally and it doesn't depend on and isn't cross-referenced to this ticket. So when you continue to update this ticket, you're not reaching any audience who can do anything about it. You're simply wasting your time and ours.)
If, as you say, it "doesn't cause a problem" then it isn't a bug. There apparently was a bug, but it wasn't tracked on this ticket and besides, the bug has been fixed now.
The problem you're referring to now is a potential bug which could theoretically become actual, if the developers inexplicably fail to prevent it despite advance notice. But as I said before, the bug tracker is not intended for speculating about future bugs. Therefore this ticket is not being used to track anything.
(If you don't know, the Bedrock developers use an internal tracking system to manage issues and generally aren't aware of updated information on Mojira unless the mods direct their attention to it. I'm told they have a ticket in their system for this upcoming change for Android 11, but they originated it internally and it doesn't depend on and isn't cross-referenced to this ticket. So when you continue to update this ticket, you're not reaching any audience who can do anything about it. You're simply wasting your time and ours.)
This bug is confirmed previously and there is also a deadline from Google. Is it potential? I don't think so.
But you're right. I shouldn't waste your time. I'll stop updating this ticket.
Our purpose is the same, we all hope to help Minecraft.
If in October there is still no version that works fine targeting API level 30, I will ask to reopen this ticket. At least, reserve enough time for developers to prepare. Is this OK?
This bug is confirmed previously and there is also a deadline from Google. Is it potential? I don't think so.
But you're right. I shouldn't waste your time. I'll stop updating this ticket.
Our purpose is the same, we all hope to help Minecraft.
If in October there is still no version that works fine targeting API level 30, I will ask to reopen this ticket. At least, reserve enough time for developers to prepare. Is this OK?
Rather than reopen this ticket, it would be appropriate to create a new ticket with the facts and symptoms that are actually occurring at the time, if the problem fails to be avoided. If a lot of what you've provided here is still relevant, it should be easy to copy it to the new ticket so I don't think it would be a big burden, and doing it that way would leave us with a less ambiguous/confusing history. Thank you for understanding.
Rather than reopen this ticket, it would be appropriate to create a new ticket with the facts and symptoms that are actually occurring at the time, if the problem fails to be avoided. If a lot of what you've provided here is still relevant, it should be easy to copy it to the new ticket so I don't think it would be a big burden, and doing it that way would leave us with a less ambiguous/confusing history. Thank you for understanding.