Hey there, thanks for raising this!
I was able to reproduce, and I've filed a non-paging incident to address this, since this shouldn't have any impact on existing production apps, and will only impact creating/developing new custom components on cloud. Engineering will take a look first thing when they come online in a couple of hours and we will likely roll back cloud to fix this. So I expect we'll see a fix later today
Cheers,
Isaac
1 Like
Thanks Isaac. Will check later today to see if it works.
FYI: You marked this as solved, but right now I'm still seeing the same error.
Just to bump this one again, we're seeing the same issue and it is affecting a production app that we have. We are in need of replacing an older component that is no longer supported by Retool, with the React version of the same, and as a result of the bug we can't build the replacement, meaning this service is down. If we could get an update on this that would be appreciated.
I can confirm this is fixed for me now. Thank you Isaac!
Yep, just to confirm, it wasn't solved when I marked as solved, I did that to bring awareness to folks reading up on the thread that we would be looking into it when engineering came online.
We did roll out a fix a couple of hours ago and it should now be fixed!
2 Likes