"ERROR! Project is not valid"

Franks

"ERROR! Project is not valid" message

Please describe what you expected to happen and what actually happened.

I wanted to save a project as a new one and clicked save with no project name applied.

How to reproduce

I just need to try to load the project and the above mentioned error message appears.

And I can't delete the "noname" project.

System info (if relevant)

Rlx version: e.g. 1.7.1

Kyriakos-Reliq

Hey @Franks ,

Thanks a lot for reporting this.

It is possible that saving the project without a name created a special project name that conflicts with another project or with part of Reliq itself. We’re already looking into this and will work on a fix as soon as we’re able to reproduce it.

In the meantime, you can try the following to recover or remove the project:

Connect Reliq’s USB HOST port to a Mac or Windows computer.
Open the Reliq Updater.
Click Transfer.
Open the Projects folder.

From there, you can try renaming or deleting the project.

If possible, you can also make a copy of the project and send it to support@reliq-instruments.com. We’ll have a closer look and do our best to restore anything if needed.

Thanks again for the report, and please keep us posted.

Franks

Kyriakos-Reliq

Hey there.
Thanks for the reply and infos.
I can't delete the project on the hardware - it always restores itself.
Applying your solutions right now.
Transfer made the project folder accessible on my Macbook.
Renaming the folder didn't change anything.
Renaming all files within the folder (add "xyz" in front of each file) didn't do anything.
Renaming both folder and files made the project accessible again.
I could load and delete it (project was empty anyways - I just falsely saved the project without giving it a name in the beginning).

Thanks for helping me there. Sending you the project right now.
Hope you can reproduce the error message and bahaviour.

best,
Frank

Kyriakos-Reliq

Hey @Franks ,

Thank you so much for taking the time to investigate this and send us the project!

We received it and were able to identify the edge case that caused the issue. We’re already working on a fix, and it should be included in one of the next updates.

Thanks again for the great report and for helping us track this one down. Really appreciated! 🙏