Hi tonyqus,
I just migrated my app to 2.0.5. I can confirm 100% that the same problem is still present and not fixed.
Thanks,
I just migrated my app to 2.0.5. I can confirm 100% that the same problem is still present and not fixed.
Thanks,