Hey @ohope, this appears to be a bug with the module and unfortunately we haven’t yet been able to investigate. Additionally, fixes of this nature will only roll out with a major SDK release so it will be some time yet before we are able to address it. I was going to recommend you make a github issue for us to track but it seems you already have.
As for a path forward, it seems like there are two options (there may be more that I’m unaware of).
Revert to SDK42 until we are able to release a fix.