I see that it mentions that this is a Perforce directory in the error message. Is it possible that the cooker is failing to overwrite a file that is marked as Read Only due to being checked into Perforce? I suggest ensuring that none of the files in your project’s Saved folder are part of your perforce repository. This could also be due to the length of the file path but that is less likely.
Have you tried packaging for any other platforms? What were the results?
just some .tmplog.txt and .tmp in that location. no tmpResult.txt file.
I packaged on another Mac. That works well. this issue just appears on one of my iMacs.I tried packaging for PC. No issues appears.
Could you provide the full log file from the packaging attempt? There could be some other messages that provide more information on why this is failing, even if they’re not specifically error messages.
Can you please ensure that you have enough free disk space on your OS Drive to fit this cooked build? As it mentions, it’s failing to write a text file and it’s not due to it not being able to overwrite if the file isn’t there as you said. I also suggest trying to package to a different location such as another drive or directly to your desktop if you can.
Packaging to ~/Downloads failed. Packaging to ~/Desktop failed. Packaging to ~/Document failed. And I tried to package to my external drive but failed. I also tried up my project and unzip somewhere on my Mac and then package. however, failed.
Can you please provide a System Report? This can be found under “About This Mac” → “System Report”. This may be able to provide some additional information about this issue.
Hardware Overview:
Model Name: iMac
Model Identifier: iMac17,1
Processor Name: Intel Core i7
Processor Speed: 4 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 32 GB
Boot ROM Version: IM171.0105.B20
SMC Version (system): 2.34f2
Serial Number (system): C02SX020GQ17
Hardware UUID: 6A6A57A2-FD8B-5F8E-9D97-493760ECE541
Is this still a problem? Maybe you could use First Aid function in Disk Utility to see if there are any permissions issues in the filesystem on this Mac?