@burning_silkworm any idea what can be done?
Hi @conservation_sheep thank you for reporting this. We are taking a look internally to investigate it, I’ll feedback here as soon as we have a fix for you!
thanks for the update
Thanks for the ping, I’ll check it out
@tiago I just checked in our project and it still breaks with the same error…
It should now be fixed. We had some caching problem with our previous deploy. Sorry for that!