Can't delete ".sandbox" files: com.apple.WebKit.WebContent.Sandbox / com.apple.WebKit.Networking.Sandbox

Question

Level 1

15 points

Can't delete ".sandbox" files: com.apple.WebKit.WebContent.Sandbox / com.apple.WebKit.Networking.Sandbox

Hi - I'm trying to delete to two files that have been apparently "sandboxed" (this occurred when I was running tasks in CleanMyMac and hit cancel rather than entering my root password), but can't figure out how to do so.

I receive an error stating that I don't have permission/can't access the file regardless if I try to zap it, drag to trash, terminal 'rm' command...etc; no luck.

Error:

/private/var/folders/3l/3s1rd2ws69q1kwtds8b4bxp00000gn/C/com.apple.WebKit.WebContent.Sandbox: “com.apple.WebKit.WebContent.Sandbox” couldn’t be removed because you don’t have permission to access it.

/private/var/folders/3l/3s1rd2ws69q1kwtds8b4bxp00000gn/C/com.apple.WebKit.Networking.Sandbox: “com.apple.WebKit.Networking.Sandbox” couldn’t be removed because you don’t have permission to access it.

Any suggestions? Thanks in advance,

MacBook, macOS 10.14

Posted on Apr 16, 2019 12:59 PM

Reply

Answer 1

BDAqua

Level 10

250,259 points

Apr 16, 2019 1:11 PM in response to MJ_rocks

Did you try the sudo rm method?

Reply

Answer 2

Apr 16, 2019 3:05 PM in response to MJ_rocks

I run CleanMyMac X before every shut down and just started having this same issue about 18 hours ago. However, I was never prompted to enter my root password like you mentioned. It just randomly showed an error under System Junk > User Cache Files when running a standard Smart Scan last night. I did have SIP disabled a while back, in order to run a custom bootloader, but I have since re-enabled it. So far, I have not found a reason or solution for this.

Reply

Answer 3

Apr 16, 2019 3:12 PM in response to BDAqua

Are you suggesting that disabling SIP will allow sandbox files to be removed by CleanMyMac X? I'd prefer not to disable it for obvious reasons, and would rather know why this issue is occurring since I've had SIP re-enabled for months now (after disabling it for ~1yr last year) and have never received this error with or without it enabled.

Reply