It is because it is still looking for the Project you added. You can remove the project manually if you go to your profile (Settings > Open Config Folder) and edit .pulsar/storage/application.json to remove the project path that no longer exists.

Alternatively you could remake that project path and then remove the project in Pulsar.

I do think that maybe we could accept an enhancement that would prompt the user to remove the missing project when it is encountered. e.g.:

Unable to open project folder...

Remove project? Yes/No

It is important to keep the option for checking simply because it can be used for projects on drives that aren't always mounted.

@Daeraxa
I love the suggestion that gives the user the option to remove the project folder.

Do we also think it'd be beneficial to add another option to find the project folder? That could then open a file view and allow the project to be reselected.

That way its:

• Exit (Ignore the popup, such as the project being on an unmounted drive)
• Remove (Remove the project entry)
• Fix (Fix the path to the project)

Seems rather like the complete set adding that, but of course I don't know how complex that may be.

That's a good point actually, it would be nice to "repoint" the project as well. I think it would be a nice QoL thing, I've certainly had this issue before and had to manually purge it.

I assume there are also project management (in the Pulsar sense) packages that can more directly interact with that file that might provide similar features as a workaround or inspiration.

any update?@@