It seems like setting the status to won't Fix is inaccurate as the status would be more accurately described as a duplicate of MCPE-161517. Which is a fairly detailed description of the issue that is causing this listed issue. It also includes a temporary fix while we wait for the developers to hopefully fix it. I would suggest anyone who followed this issue to go follow MCPE-161517 as that issue is still tagged as unresolved.
It seems like setting the status to won't Fix is inaccurate as the status would be more accurately described as a duplicate of MCPE-161517. Which is a fairly detailed description of the issue that is causing this listed issue. It also includes a temporary fix while we wait for the developers to hopefully fix it. I would suggest anyone who followed this issue to go follow MCPE-161517 as that issue is still tagged as unresolved.