Bug Report
Saving a Cloud project to your Computer with Linked Project selected doesn’t update the JSON file to pull assets from the new local asset folder.
My Experience
I had a project which was saved to GDevelop Cloud.
I decided I wanted this project stored on my local machine so I
- ‘Saved As’ and chose Linked Project File option (the other being New Project)
When I tried to open this local project the following day I encountered an error where none of my resources would load, and my Asset folder was filled with 0kb png, and wav files.
I tracked the issue down to the local project JSON file where I found the ‘Resources’ path fields were still trying to pull from GDevelop Cloud, instead of the local ‘Assets’ folder.
To make matters worse, it appeared my previous Cloud saved project versions had become corrupted and all my assets had vanished.
My Fix
Thankfully I had a local backup project from December with much the same assets.
- I opened my latest project build and ‘Save As > NEW PROJECT’ to remove any association with the previous project’s Cloud saved assets.
- I deleted all the content from the ‘Assets’ folder of the new project.
- I copy pasted over the back up asset folder contents to the new local project asset folder.
- I edited the new project file JSON; copied the entire ‘Resources’ section from the old backup to the new project JSON so it would load from the Assets folder instead of the missing cloud files.
In the end I lost maybe 20 placeholder sprites, so it could have been much worse.