I have 3 children, each one has a copy of Minecraft PE installed. THe devices are a Kindle Fire HD (Android), Galaxy Tab 2 (Android) and a Galaxy Tab 3 (Android).
All was fine, but since the game updated itself, none of the devices has been able to connect to another realm (the option is just not present).
I don't feel that any screenshot will do justice, as I can see that this seems to be getting reported by MANY people now.
What I'd like to see happen within the next week, is:
A. Get this issue resolved.
B. Provide a way to revert to the previous "working" version.
C. Return the cost of the product on each device and I will get it uninstalled.
Seems a fair request, as you seem not to be too bothered about providing a fix, and as none of the kids now want to play minecraft, because of this issue that YOU caused, I'd like a return of their pocket money they spent to get this bug ridden game.
Thankyou
A very disappointed set of users
Linked issues
duplicates 1
Comments 4
Duplicate of MCPE-6672 – If you have not, please use the search function in the future, to see if your bug has already been submitted.
A workaround has been provided on that ticket.
So, I log an issue, to which after over a year you finally reply.
I work in software testing and can tell you, your testing of such fixes ( as suggested on #MCPE6917), is not valid as the tablets and OS differ.
In the case of the three tablets in our house, your suggested fix does not work.
Given your inability to reintroduce a splendid feature that WAS present, I can only offer advice that you maybe need to employ developers that know what they are doing.
Also, the workflow of your bugs does not give scope for an issue you think will be rectified, to be reopened. This will then cause another bug to be logged, for the exact Same issue; which will undoubtably open for another year before someone looks at it.
I am very sorry that you failed to attempt to contact me before closing the issue, as you would have then been in a position to attempt debugging (you may need to google that word).
Sent from my iPhone
> On 22 Aug 2014, at 19:45, "[MCPE Mod] sbd01 (JIRA)" <[email protected]> wrote:
>
>
> [MCPE Mod] sbd01 resolved an issue as Duplicate
>
> Duplicate of MCPE-6672 – If you have not, please use the search function in the future, to see if your bug has already been submitted.
> A workaround has been provided on that ticket.
> Minecraft Pocket Edition / MCPE-6917
> v0.8.1 alpha
> Change By: [MCPE Mod] sbd01
> Resolution: Duplicate
> Status: Open Resolved
> Add Comment
>
> This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
>
So, I log an issue, to which after over a year you finally reply.
I work in software testing and can tell you, your testing of such fixes ( as suggested on #MCPE6917), is not valid as the tablets and OS differ.
In the case of the three tablets in our house, your suggested fix does not work.
Given your inability to reintroduce a splendid feature that WAS present, I can only offer advice that you maybe need to employ developers that know what they are doing.
Also, the workflow of your bugs does not give scope for an issue you think will be rectified, to be reopened. This will then cause another bug to be logged, for the exact Same issue; which will undoubtably open for another year before someone looks at it.
I am very sorry that you failed to attempt to contact me before closing the issue, as you would have then been in a position to attempt debugging (you may need to google that word).
Sent from my iPhone
> On 22 Aug 2014, at 19:45, "[MCPE Mod] sbd01 (JIRA)" <[email protected]> wrote:
>
>
> [MCPE Mod] sbd01 resolved an issue as Duplicate
>
> Duplicate of MCPE-6672 – If you have not, please use the search function in the future, to see if your bug has already been submitted.
> A workaround has been provided on that ticket.
> Minecraft Pocket Edition / MCPE-6917
> v0.8.1 alpha
> Change By: [MCPE Mod] sbd01
> Resolution: Duplicate
> Status: Open Resolved
> Add Comment
>
> This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)
>
Duplicate of MCPE-6672 – If you have not, please use the search function in the future, to see if your bug has already been submitted.
A workaround has been provided on that ticket.