New release already has solution to that, but iOS 1.5.0 taking bit longer time... but soon fix will be available for iOS users as well...
You are viewing a single comment's thread from:
New release already has solution to that, but iOS 1.5.0 taking bit longer time... but soon fix will be available for iOS users as well...