Handling export conflicts for unsaved projects

When you create and export a canvas without signing in, the project is automatically assigned a project ID. If you come back the next day and create a new canvas, but you’re not signed in again, the new canvas will be assigned a different project ID. If you try to export this new canvas to the IDE project from the first day, you will encounter a conflict, as the project IDs don't match.

If you were not signed in on Day 1 and did not save the project link (since the canvas is tied to the browser session), you may lose access to your previous project, making it impossible to export directly into the IDE project from Day 1.

How the Conflict is Handled

When you attempt to export a new canvas on Day 2 and the system detects a mismatch in project IDs (as outlined in the warning message), it will also display a link to the lost canvas from Day 1. This lost canvas is still accessible, tied to the IDE project ID from the first day.

Step-by-Step Resolution:

  • In the warning message, click on the link labelled "Recently Imported Canvas".

  • This will open the non-signed-in editor with the unsaved canvas from Day 1.

VS Code Terminal: In the warning message, click on the link labelled "Recently Imported Canvas" to access the unsaved canvas

2. Rename and Save the Canvas:

  • In the editor, rename the canvas to give it a proper title.

  • Sign in to your JSX.Design account to save the canvas to your profile.

3. Access Your Projects:

  • Click the Home button on the top-left corner of the editor. This will take you to the project dashboard.

  • You will now see the newly saved canvas under an Unnamed project.

4. Create a New Canvas in the Same Project:

  • Inside the project dashboard, click on the Unnamed project.

  • From here, you can create a new canvas under this project, redo any work you intended to do on Day 2, and export it without any conflict.

Conclusion

By following these steps, you can resolve any project ID conflicts and keep your work organized under a single project. To avoid these issues in the future, we recommend signing in before starting a new session, ensuring that your projects are properly saved and linked.

Last updated