objective-c - quick - xcode tutorial objective c
NSRemoteView generates a strange message in the Log (2)
When I run my sandboxed application in macOS Sierra, I find this message in the Log :
2016-09-21 12:08:42.787003 MyApp[1505:63581] warning: <NSRemoteView: 0x610000123160> determined it was necessary to configure <NSVBSavePanel: 0x103e002a0> to support remote view vibrancy
I don’t see this message in OS X 10.11.
It seems that this message appears when the application displays a NSSavePanel that covers the main window.
I’ve verified the .xib file that contains the window, I’ve searched in the documentation of Xcode and with Google but I didn’t find anything to solve the problem.
Added sept, 22
As soon as I declare a NSSavePanel in a method :
NSSavePanel *panel = [NSSavePanel savePanel];
The message is sent to the log.
Try to find answers here:
- Accessibility API stops working after sandboxing
- Sandbox entitlement to script iTunes via NSAppleScript
- 'xattr' command not working inside sandbox app
Also, may help:
<key>com.apple.security.scripting-targets</key> <dict> <key>com.apple.security.temporary-exception.apple-events</key> <array> <string>com.apple.terminal</string> <string>com.googlecode.iterm2</string> <string>com.apple.finder</string> </array> </dict> <key>com.apple.security.temporary-exception.shared-preference.read-write</key> <array> <string>com.apple.finder</string> </array> <key>com.apple.security.temporary-exception.apple-events</key> <array> <string>com.apple.terminal</string> <string>com.googlecode.iterm2</string> <string>com.apple.finder</string> </array> </dict>
!!! If you try to submit to AppStore be informed that apple do not allow do this:
- com.apple.security.temporary-exception.apple-events and
macOS applications follow the pattern of sandbox. This means that you need to explicitly allow your application to read/write files, otherwise you encounter a permission problem that trigger some errors (one of them is in the form of the warning that you have underlined).
On the Capabilities tab of your application, be sure to enable at least one of the file access methods.