Hi Beslind,
We believe we hava fix for this. You can check it out here: b53db70. To be clear, we think this was only occuring with enums that were saved from a 4.9 preview build. Is that possibly the case here? I want to make sure we correctly resolved the issue.