@Flak was the issue closed because it couldn’t be reproduced on a future build or did the team failed to reproduce it with the provided project + public v35.00 version? I specifically made sure the project is in a state where the issue can be reproduced.