Issue MCPE-46543 has been open for an extended period of time, apparently has been erroneously marked as resolved previously, and yet has persisted across versions. Multiple users have reported that this error occurs despite clearly having sufficient storage available, and being well under 2gb of total local data as reported by the Xbox System App. This is a game-breaker, and yet seems to have gotten little traction, likely due to the diffulty in reproducing the bug.
In my programming/application support experience, there is really only one explanation for erroneous messages such as this: something else is being checked, besides local storage space. I'd like to understand whether this is a direct conditional, or one inherited through a library/system call, and what the nature of any additional constraint(s) might be.
This is not a duplicate of the existing issue, but a separate request for information that might help isolate the existing issue for reproducibility. Please review the relevant code which triggers this message, and document any other internal conditions that are checked by this function/method/etc, and which might thus falsely render this error. If no other such conditions exist within the Bedrock codebase directly, please document the specific library/system calls that are made to verify the storage condition, so that other systemic causes (i.e. disk quotas, lack of temp space, etc) can be further investigated.
Attachments
Comments 6
This is not invalid, it is an appropriate "bug report", as this "error message" clearly fails to accurately describe the conditions which lead to the error. There is also an obscenely long-unresolved bug which breaks the game, and the resolution of which may depend on this issue.
Community support cannot help, because this analysis requires access to the source code.
This is the appropriate place for this - and the only appropriate place for this. If you have any uncertainty about this, I suggest you escalate to someone who has a better understanding of advanced RCA (Root Cause Analysis).
I am a programmer and highly experienced application support analyst with a special emphasis on RCA. You are getting my expertise for free, because I love the game. I would strongly suggest against blowing off this opportunity to help the hundreds/thousands of individuals who are suffering from the original bug.
If you have information to add about this issue based on your expertise, the best place to do that is on the MCPE-46543 report. Regardless of the age and history of that report, that is where this issue is tracked, and where the developers are most likely to look for information when they are working on a solution.
However, it appears that you are suggesting that additional documentation be created. That in itself is not a bug in the game, and is actually a feature request, which is also invalid for this bug tracker.
For more explanation, please see the Bug Tracker Guidelines.
I understand how it appears to you, but this is neither a duplicate of the other issue, nor a feature request.
This is reporting a significant flaw in the Bedrock code as regards internal error/exception handling. Documenting the current behavior outside of the code itself could serve as a workaround, which is why I left some ambiguity on the exact meaning of "document". However, the actual appropriate place to make the change is in the source, by rendering a different error which "explains" the actual problem to the end user.
This error message does not indicate what the plain text suggests it should, and that is a bug. The permanent solution is more ambiguous, because I cannot read the source. There's more than one possible construct that can create this issue, and resolution depends somewhat on Mojang's build system and internal coding style policies. In other words, it's related to the other issue, but not the same, and I can't be more specific without presuming to tell them how to code it directly. It's 100% a bug though.
It is true that many of the error messages encountered in the game do not provide any useful information to the user, such as
Unable to connect to world
World is corrupted
An error occurred (happens when uploading to a realm)
You are (almost) out of storage space
That could be considered a design flaw. However, the choice made for this bug tracker is to accept reports that describe the circumstances leading to each of these error messages, preferably with reproducible steps. Generally, all reports resulting in the same error with substantially similar steps will be consolidated and tracked as a single issue, though sometimes they are kept separate by device.
So these seem to be the options:
Ask that all error messages be enhanced to describe the actual (or possible) causes. This would be considered a feature request and therefore invalid for the bug tracker. The place to suggest this is on the Feedback Site
Submit a general bug report to the effect that "error messages do not include information about the cause of the error". This would be invalid as it would mention multiple issues in a single report and would therefore be rejected.
Submit a bug report for a specific error message that it does not contain information about the cause. This would be merged into the existing report (if there is one), as in the case of the out-of-space message.
Add a comment to the existing open bug report.
I believe your best option would be the last one, and a suggestion for that specific issue might be considered when (or if) the developers are working on it. For greater visibility, you can even submit a request on the Mojira Discord after you make such a comment to add that information to the Description where it is more likely to be seen by a developer.
Thank you for your report!
However, this issue is Invalid.
This is a technical question; this site is for bug reports only.
Please contact Community Support for assistance and refer to this ticket by providing a link.
You might also visit the Mojira Discord to discuss bugs and bug reports.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki