The problem is still present in the latest version, I had it represent a number of times across different projects and situations, one workaround is to set the custom prop to a value on the component onStartup event before actually using it. Definitely a nasty bug needing a fix in the future