Yes, it still doesn't work in 1.0.8 either. It is being looked into. Hopefully there will be good news soon.
Version 1.0.9 is now starting to slowly roll out to users.
I just got the 1.0.9 update and this hasn't been fixed yet.
I'll look into this, but maybe it's in the pipeline and the fix will be in a future update soon.
Yeah hopefully this will be fixed in a future update. I'll keep you updated.
I mean good. And great. Great and good.
I'm sure you already know this, but the bug still exists in v184.108.40.206.
Oh, and welcome back from your vacation! How was it?
This bug is still present in 220.127.116.11.
It seemed like it was close to getting fixed for a while there. Is the fix still scheduled for inclusion in an upcoming release?