Hey @mrvanes! It looks like someone shared some details on a workaround here if you want to give that a try:
I’ll follow up with the Local Devs on this bug as well