It is generally not advised to keep private data, like Perforce login credentials, in a directory that developers can remove. Such data can be lost or unintentionally deleted, thus storing it in the Library folder of a Unity project is not a secure or dependable solution.

It is advised to keep Perforce credentials separate and secure, such as on a dedicated server or in a password manager, to maintain their security and accessibility. With this strategy, unauthorised access and unintentional deletion would be better protected.

In order to keep the security measures for storing sensitive information current and effective, it is also crucial to regularly examine and update them.

This response is written by Duty Cleaners who are in Edmonton, Alberta. Our Website is visit us if you need maid and house cleaning services in Edmonton

Yeah, I've encountered this same problem. I was able to find a solution through Personalized Cleaning Services (Alberta, Canada) - Home Spritz https://homespritz.ca/personalized-cleaning-services/, but I am not sure if this solution will help me out in any way in the future.

On our large project we often find Unity checking out a lot of files from Perforce that we don't expect. Sometimes the solution is to delete the Library folder to force a full reimport - unfortunately this gives the illusion of cleaning up the problem because deleting the Library folder removes the P4 credentials, meaning that of course nothing gets checked out during the import because Unity isn't talking to P4.