The reference screenshots disappear when released

Japan Forum
1

After releasing to Orchestrator, the reference screenshots for the activities disappear when the package is extracted. Is there a way to handle this?
I would like to know if there are any measures, such as including the “.screenshots” folder in the publish.

2

Hello

If you’re going to do it, you should copy the .screenshots folder and also save the screenshots (without the dot) folder, and if you need to restore it from the nupkg, you should rename the screenshots folder to .screenshots, right?

3

Thank you for your continued support.
This is Gima from UiPath Technical Support.

I would like to contact you regarding the matter you inquired about:
“The reference screenshot disappears after release”

Here are the details:

[Report Content]

I understand that you are inquiring about the issue where the reference screenshot disappears after unpacking the package released to Orchestrator. Is there a way to address this?

From the information you shared, it seems that you are inquiring about the phenomenon where the reference screenshot of the activity does not appear when checking the package after releasing it to Orchestrator.

According to the official UiPath guide, the reference screenshots are saved in a hidden folder called “.screenshots” under the project.

All screenshots are automatically saved in another folder called “.screenshot”, as “.png”, in the same location as the project. By default, this path is
C:\Users\your_user_name\Documents\UiPath\your_project_name.screenshots

The above document explains that the reference screenshots are separate files stored in the same location as the project. The official guide for Studio also states that it is necessary to obtain the entire project, including the “.screenshots” folder, not just the “.xaml” file.

Therefore, if you only use the unpacked released package as the editing source, the reference screenshots from development may not be maintained and may not display.

In light of this behavior, to maintain and edit with the reference screenshots intact, it is recommended to keep the original development project along with the “.screenshots” folder.

  • Keep the original development project intact and use that during maintenance
  • Since the “.screenshots” folder is a hidden folder, please enable the view settings as needed to check it
  • If the project is maintained by a team, register the entire project in source management systems like Git or TFS

If the original development project remains, by keeping the “.screenshots” folder as well, it may be possible to edit while maintaining the reference screenshots.

That is all for my communication. Thank you for your attention.