App affected by sandbox

With App Sandbox, you can't have a custom file browser. Use the NSOpenPanel or NSSavePanel classes instead. For a sandboxed app, they actually run in separate, more priveleged processes that are able to dynamically grant access to the specific URLs the user selects. A more thorough description of how all this works is available here: App Sandbox Design Guide

First of all thanks for the answer.

I have read that documentation before but it didn't fully solved my case. The point is that the first version of the app worked and it was released in mid 2014 so i guess that i also used Sandbox and i think it was not until the last part of the year 2015, when i updated the app and it started to go wrong. It may be weird but it is true. That is reason why i am confused.

So you've had it in the store for a while and it worked until recently? That could happen for a variety of reasons, including changes to OS X, changes to Unity, or even something you might have done. At any rate, stuff like that isn't supposed to happen (unless, of course, you were accidentally taking advantage of some security loophole that has since been closed). You might want to file a bug report, but if your app was able to do some sort of unrestricted file browsing in the past, I highly doubt that they would offer help getting it back.

Thanks again.

I will file a bug report hoping that i could get more information. If not, i will use the Developer Technical Support.

If i get some interesting information i will post it here.

Cool. Sorry I don't have any specific advice to offer. 🙂

So…was it a custom file-browsing system done entirely within the app? Technically, that should have never been possible under App Sandbox…

Yes, i used Unity classes, the typical ones such as Directory or Path plus the GUI buttons that are offered. What i am surpised is that Unity, being a really portable engine in terms of app distribution, has this defect when it comes to sandboxing. I thought that when a user chooses Mac OS X as platform in Unity it will automatically translate the required thing so it gets something compatible with NSOpenPanel or NSSavePanel.

Yes, I agree with you that it's a reasonable assumption. Was the version of Unity you used in the past the same one that you're using now? That would help you figure out if it's a change in Unity that's causing the change. You might also want to pull an older version of your app (the one that used to work) out of your backup or SCM repository and test it on the current OS X—that would help determine if it's a change in OS X.

Good point. I am going to download a past version of Unity.

None of both approaches worked so i guess that it is the OS X. I will mark the first answer as correct.

Thanks a lot bob133

Glad to help where I can. Good luck with your continued work! 🙂