Closed zetxek closed 3 years ago
Hi @zetxek , Thank you for opening and reporting this issue. We have created an internal task for this issue and will try to come back to you as soon as possible. Thank you for your patience!
Hi @zetxek , Thank you for opening and reporting this issue. We have created an internal task for this issue and will try to come back to you as soon as possible. Thank you for your patience!
thanks! Also, please mind that I don't think it's a fatal error - but a Warning.
Hi @zetxek,We are happy to share that we've just released the new 1.4.1 version with a fix for this issue. Thank you again for the detailed reports and patience. We are closing this issue now but please feel free to reopen the issue if this still occurs.
An issue found in our production environment, while checking the logs:
It seems that the address parser might be missing some error handling/data validation before doing operations on the strings.