com.github.facebook.watchman.plist for write: Permission denied

I am studying react-native.And I follow the tutorials on the website.When I execute “react-native run-ios”. It happens some error messages.

Looking for JS files in
   /Users/Mapple/Developer/React-native-workspace/HelloWorld 

[19:16:32] <START> Building Dependency Graph
[19:16:32] <START> Crawling File System
[Hot Module Replacement] Server listening on /hot

React packager ready.

2016-07-30T19:16:32,265: [cli] Failed to open /Users/Mapple/Library/LaunchAgents/com.github.facebook.watchman.plist for write: Permission denied

2016-07-30T19:16:32,265: [cli] Failed to open /Users/Mapple/Library/LaunchAgents/com.github.facebook.watchman.plist for write: Permission denied

Watchman:  watchman--no-pretty get-sockname returned with exit code null 2016-07-30T19:16:32,265: [cli] Failed to open /Users/Mapple/Library/LaunchAgents/com.github.facebook.watchman.plist for write: Permission denied

 ERROR  watchman--no-pretty get-sockname returned with exit code null 2016-07-30T19:16:32,265: [cli] Failed to open /Users/Mapple/Library/LaunchAgents/com.github.facebook.watchman.plist for write: Permission denied

Error: watchman--no-pretty get-sockname returned with exit code null 2016-07-30T19:16:32,265: [cli] Failed to open /Users/Mapple/Library/LaunchAgents/com.github.facebook.watchman.plist for write: Permission denied

    at ChildProcess.<anonymous> (/Users/Mapple/Developer/React-native-workspace/HelloWorld/node_modules/fb-watchman/index.js:198:18)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:850:16)
    at Socket.<anonymous> (internal/child_process.js:323:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:492:12)

I find there is no file-com.github.facebook.watchman.plist in the /Users/Mapple/Library/LaunchAgents. I tried a variety of ways, but it does not play a role。

[olsio]

@brianarpie deleting the directory might delete other LaunchAgents a better solution would be to update the user:

sudo chown -R $(whoami):staff ~/Library/LaunchAgents

In my case the offending party was LastPass, I raised a bug with them, the installer seems to create the directory as root.

[brianarpie]

@anil826 my guess is ~/Library/LaunchAgents is still owned by root. You can resolve this by deleting the directory and creating it as the current user. The following worked for me:

rm ~/Library/LaunchAgents
mkdir ~/Library/LaunchAgents

cheers