App Sandbox issue on OSX 10.8 - macos

I'm using the following App Sandbox Temporary Exception Entitlements in my Mac app.
com.apple.security.temporary-exception.apple-events com.apple.iTunes
com.apple.security.temporary-exception.files.home-relative-path.read-write /Music/iTunes/iTunes Media/
If I build my app in OS X 10.9.4 with enabling App Sandbox, and run it in OS X 10.8.5, my app reports App Sandbox is enabled in activity monitor. But get an error which I coded.
If I build my app in OS X 10.8.5 with enabling App Sandbox, and run it in OS X 10.8.5, my app reports App Sandbox is not enabled in activity monitor. Then my app runs without any error.
I can't understand why this kind of phenomenon occur. I don't touch any code in 10.9.4 and 10.8.5. Please help me!
Do I need provide two version which is App Sandbox enabled one and not enabled App Sandbox for my app?
Also, Apple rejects "temporary-exception" used app. Is that true?
I'm not joind with Apple Developer Program, but if my app have possibility to delivered in Mac App Store, I will join with Apple Developer Program.

Related

Mac app rejected as not open in new mac OS 10.14

I have submitted app twice in mac app store and they have rejected with below reason.
Guideline 2.3 - Performance
Your app does not achieve the core functionality described in your marketing materials or release notes.
Specifically, App does not launch from Finder. App icon momentarily appears on Dock but quit itself before being launched.
Best regards,
App Store Review
While I further followed up with apple then they have informed that app is not open in mac 10.14 OS.
Have any one face similar kind of issue and what is resolution steps for such kind of issue?

Could not connect the action buttonPressed: to target of class NSApplication when attempting to debug Mac OS X app on 10.7

I'm attempting to target 10.7 with my Mac OS X app, but when I try running it on a 10.7 machine no window opens and I get "Could not connect the action buttonPressed: to target of class NSApplication" logged to the console.
When I try to build the app locally to debug, I get "-fobc-arc is not supported on platforms using the legacy runtime". It looks like I need Xcode 5+ which isn't supported on 10.7 so I'm at a loss for how to continue debugging this issue.
I found an answer from another question. 10.7 doesn't support storyboards.
https://stackoverflow.com/a/30954258/873546

Crash when running a new app where iCloud is on

I just wanted to try to code an OS X app using iCloud so I created a new project then set iCloud on:
Because of iCloud's reputation, I ran the app without any modifications just to see if it works but I have this error (after an alert "Build succeeded"):
I didn't write any code on this project, so what could possibly be wrong? I'm using Xcode 6 Beta 3 on OS X Mavericks, when I'm running other apps from Xcode it works and when I run the app with iCloud set to off it works too.

Use jack os x in a sandbox Mac application

On my Mac OS X application released on the App Store, I want to be able to use a Jack OS X audio device as an input but the device does not appear in the list returned by portaudio. When checking the logs in the console I see:
31/01/2014 10:11:35.000 kernel[0]: Sandbox: MyApp(xxx) deny network-outbound /private/tmp/jack_default_501_0
Is there some extra permission I should add to my entitlements file to be able to access this device properly? This device properly appears/works when using testing my app without the sandbox enabled.

Application is not working on 10.6

I'm currently working on a port of my Windows game for Mac OS X, it runs fine on my Mac when compiled with Xcode 4.5.2 on OS X 10.8, but it crashes on a friends Mac running 10.6. At first I thought it was due to one of the Frameworks I've been using, but the standard Cocoa app template crashes at well, without any visible error message.
I already tried setting the Deployment Target to 10.5, but this doesn't change anything. When starting the App, it appears for a short time in the Dock and then disappears without showing any kind of UI or error message.

Resources