I am able to reproduce this behavior, albeit a little inconsistently, and will talk to our internal teams about further diagnosing and fixing the issue.
Hey @gtourkas - this is a fairly high priority issue for the team, as we are currently putting an emphasis on supporting custom components. It has been difficult to consistently reproduce this particular issue, however, so I can't confidently give a timeline. As soon as I have an update, though, I'll follow up here!
Hey @gtourkas - sorry to hear that you're still having issues. Thanks for including a screen capture, though!
Which parts of the app are being rendered by the custom component? Just the inputs? Or the text, as well? Also, do you see any errors in the browser console when the custom component isn't showing up?
Last but not least, is this a consistent issue or does it only happen intermittently? Even when I reproduced the behavior initially, it seemed to happen very inconsistently.
It occurs also on the custom component that simply prints a "Hello !", which is what a submitted as problem in the first case.
Inspecting with the Developer Tools, the IFrame that is supposed to be used for loading the custom component doesn't show up. The "fetching mask" div does:
Hey @gtourkas - our engineers are pretty confident now that they've narrowed down the scope of the issue and shipped a fix. Can you verify on your end?
