Still not fixed in v 16.0.5, update from Google Play - what gives?
@[Mojang] MissMarzenia (Aleksandra Zajac)
I'm sorry, but I think you're mistaken.
You DID comment it was reported for testing - in V13
In v14 it was subsequently fixed.
In v15 the fault reappeared and this bug was re-opened.
Since then, you have not told us you have reported this for testing in V15.
Has this been reported for testing in V15?
Thanks in anticipation.
Sorry, my mistake, it is fixed, it just feels different to use somehow... longer press perhaps? Cheers.