Scirra
current beta corrupts project (no repro)
Problem description
I don't have a repro yet. But as it's so severe I am still reporting it.
Multiple users are affected with same error.
Attach a .c3p
I sent an email with a corrupted project to Ashley in case that may help.
Steps to reproduce
Observed result
Expected result
More details
Affected browsers/platforms:
First affected release:
System details
View details
PASTE HERE
Same issue here: https://www.construct.net/en/forum/construct-3/how-do-i-8/invalid-project-file-error-186092
This looks like a regression involving the Instances Bar and/or hierarchies - assigning to @DiegoScirra to investigate. I suspect this change in r437:
Instances bar: inconsistent state after setting a hierarchy through the bar which could lead to crashes
If that clue helps anyone find steps to reproduce it would be helpful.
I don't think the project corruption is too serious - I believe it will be possible to patch the next release to successfully open any projects that have been affected by this issue and can no longer be opened in r437. The reason the project appears to be corrupt is in a layout JSON file, there is an entry that looks like this:
"scene-graphs-folder-root": {
"items": [null, null, null, null, null ...
Any null entries cause the project to fail to open. However if you replace that with an empty array so there are no nulls as shown below, then the project opens again.
"scene-graphs-folder-root": {
"items": []
I think this might mean you possibly lose some folder organisation in the Instances Bar - hopefully there aren't any more serious issues with that - @DiegoScirra would need to confirm.
Just dropping a line here to let you know it happened to me too. I'm going to try to manually fix as you suggest.
The fix worked! Just as a mention, because I had seen mention of the Instances bar in the release notes I opened the instances bar for maybe the first time ever. I never made any edits through it or did anything with it other than having it open, but it was open when these errors occurred. Thanks for coming up with a fix protocol so quickly. Good luck with the repro hunt.
This was caused by attempting to fix #8525.
The next beta will fix the root issue and add a few extra checks when loading projects so this kind of data can be loaded without crashing. Data will be lost in that case though.
