Once again, thank you for taking the time to report this @oppi!
With 1.3.4.7, this should now be fixed:
Kindly let me know if this is the case on your end.
Thank you in advance.