UnauthorizedAccessException when using Unity Perforce integration

When using Unity's Perforce VCS integration, AAS fails to update addressables_content_state.bin when building player content due to the file being readonly. This causes an UnauthorizedAccessException exception to rise:

In Perforce, you have to manually check out assets prior to editing them in order to make them writable. Checking out addressables_content_state.bin helps to fix this issue. Unity usually does this for you automatically if you are indirectly editing an asset (e.g., by updating project settings or saving scene changes) as opposed to direct asset editing using the inspector. Therefore, the expected behaviour would be the AAS checking out addressables_content_state automatically before updating if Perforce integration is active. Please consider adding this feature in future updates!

 

Definitely, thanks for the suggestion.

 

This is still occurring with the 1.5.1 release of addressables. Is there an ETA on this fix?

 

I don't know but I also encounter this issue with git on my CI/CD build.
How would I fix this with gitlab CI/CD process?

 

Oh never mind, it's my fault. I used wrong path for the addressables_content_state.bin file.