Mac App Store Sandboxing - getting some Sandbox: storeuid deny messages

I've followed all the directions on this thread: http://forum.unity3d.com/threads/found-a-way-to-sandbox-unity-osx-stand-alones-for-mac-app-store.100916/

When I do all of the steps, everything seems to be working well and no errors occur. So then after I install the pkg file, it puts my game into /Applications and I try running it.

First I get a prompt for the App Store Developer login, enter my credentials and then I get an error saying the app is damaged and re-download from the app store.

In the Console I see several Sandbox deny errors. Do I need to worry about these and is there a way to prevent them? I cannot actually run my game after it's all signed and built:

 5/9/16 7:29:16.658 PM lsd[254]: LaunchServices: Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist
 5/9/16 7:29:17.311 PM com.apple.xpc.launchd[1]: (com.meierdevelopment.grimmwald.474912[50566]) Service exited with abnormal code: 173
 5/9/16 7:29:17.000 PM kernel[0]: Sandbox: storeassetd(376) deny(1) file-read-data /dev
 5/9/16 7:29:31.000 PM kernel[0]: Sandbox: storeuid(5347) deny(1) mach-lookup com.apple.inputmethodkit.launchagent
 5/9/16 7:29:31.000 PM kernel[0]: Sandbox: storeuid(5347) deny(1) mach-lookup com.apple.inputmethodkit.launcher
 5/9/16 7:29:31.000 PM kernel[0]: Sandbox: storeuid(5347) deny(1) mach-lookup com.apple.inputmethodkit.getxpcendpoint
 5/9/16 7:29:31.000 PM kernel[0]: Sandbox: storeuid(5347) deny(1) mach-lookup com.apple.inputmethodkit.launchagent
 5/9/16 7:29:31.000 PM kernel[0]: Sandbox: storeuid(5347) deny(1) mach-lookup com.apple.inputmethodkit.launcher
 5/9/16 7:29:36.000 PM kernel[0]: Sandbox: storeuid(5347) deny(1) mach-lookup com.apple.inputmethodkit.launchagent
 5/9/16 7:29:36.000 PM kernel[0]: Sandbox: storeuid(5347) deny(1) mach-lookup com.apple.inputmethodkit.launcher
 5/9/16 7:29:36.000 PM kernel[0]: Sandbox: storeuid(5347) deny(1) mach-lookup com.apple.inputmethodkit.getxpcendpoint
 5/9/16 7:29:37.822 PM akd[332]: success
 5/9/16 7:29:38.207 PM akd[332]: success