even if space cannot be seen updating version doesn't allow downloading new space if it was previously there

[juancarlosfarah]

In the new version, old spaces are not visible, even if they are still in the database.

When a teacher tries to download a space, if it is in the database (even if it's not visible), it throws the duplicate error.

What should happen is that either (1) when update happens / app is opened, a safety check runs so that "orphan" spaces are made visible, (2) when update happens / app is opened, a safety check runs so that "orphan" spaces get deleted, (2) when download is attempted, if space is there, it gets deleted and the new space is downloaded. Or maybe something else?

To consider: are files also necessary to deal with?

To reproduce:

1. Using an old Graasp Desktop, say 15.0.
2. Save a space.
3. Update to new Graasp Desktop 15.5+.
4. Try to save space.

Expected Output:

Space appears on the saved spaces tab.

Actual Output:

Duplicate error.

[pyphilia]

@juancarlosfarah I couldn' reproduce the error. In fact it should work, especially in the case you are mentioning, since spaces are always saved in spaces (it didn't change between versions) and all spaces are displayed for every user.

We can talk about it when you have time, but a solution which could suit every next release would be to check whether the database structure matches with the next release. If it is not the case (a breaking change might happen) we create a backup of the database (json as well as zipping all the spaces) so that the user can import it again if necessary and erase the database.