#i passed --allow-write, why does this happen?

10 messages · Page 1 of 1 (latest)

livid basalt
#

i'm already passing --allow-write

image.png
livid basalt
#

apparently this is a safety hardening

#

seems --allow-run=chrome doesn't have this problem

#

keywords for future searchers:

  • NotCapable: Requires write access to " path ", run again with the --allow-write flag
  • astral
  • cache
  • chrome
  • chromium
  • allow run breaking allow write
  • unexpected --allow-write error
#

nvm it didn't

#

it downloaded it but didn't allow launching it

#

sigh

#

how do i turn off the hardening???

#

sigh