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,
