Posts

Post not yet marked as solved
1 Replies
Well, today the missing apps were put back. Miracles do happen :-)
Post not yet marked as solved
7 Replies
Why is the app behaving differently on your Mac? I noticed that the app has in the System Settings -> Privacy and Security -> Files and Folders -> the app -> Downloads folder enabled Not sure if this was done manually in the past or as part of the installation and it somehow disappeared. How to achieve your final goal? The URL is within the sandbox. As explained above the app sandbox was configured in XCode and AppStoreConnect as well the privacy key to access the Downloads folder was added in Info.plist. See the attached images. Regardless if the Downloads folder is a simlink or not the swift code snippet should be capable to open it. It looks like that the NSWorkspace does not function properly. It does not check the app sandbox for the Downloads folder and does not ask the user for permission to access it. With regards B, I don’t think there’s a way to achieve your goal as specified. Yes, there is. Voila the solution. Not the best, but at least it works as expected. func shell(_ command: String) -> String { let process = Process() let pipe = Pipe() process.standardOutput = pipe process.standardError = pipe process.arguments = ["-c", command] process.launchPath = "/bin/zsh" process.standardInput = nil process.launch() let data = pipe.fileHandleForReading.readDataToEndOfFile() let output = String(data: data, encoding: .utf8)! return output } let result = shell("open Downloads") Conclusion Apple should investigate how the NSWorkspace functions beneath. My use case above should be working. The documentation about the App Sandboxing still mentions entitlement files, which are nowhere to be found nor possible to be added anymore. Seems the entitlements have been moved to the AppStoreConnect. The docs online need some updating as well.
Post not yet marked as solved
7 Replies
The same as in your case. This seems like a bug to me. My app is properly sandboxed both in the XCode and in the AppStoreConnect as well it contains the correct permission key in the Info.plist to access the Downloads folder. The NSWorkspace instead of raising the error that you do not have permissions, should ask for permissions instead. It should be the user to allow or disallow the access. Anyway I figured out another way that works properly. Now the app asks for the permission to access the Downloads folder before launching the Finder app.
Post not yet marked as solved
7 Replies
The Info.plist contains the NSDownloadsFolderUsageDescription key with proper description. The AppStoreConnect contains under the App Sandbox Information the following key com.apple.security.files.downloads.read-write with proper description.
Post marked as solved
66 Replies
We are in August 2021 and the problem still persists. Tried with 3 different emails, same problem. Not able to create the sandbox tester. None of the emails was ever used with Apple. In Google Play Console you add the sandbox tester which is called the license tester without any problems. Not only that, also creating in app purchase products is a nightmare. They have to go through the review process and the review gets rejected. Then you are asked to submit a new binary, however you did not manage to test it because of not being able to create the sandbox tester. Actually you are spinning in circles. On Google Play there is no review. Just create the product, implement the API, create the license tester and test. Way more convenient. Hope these issues disappear with the release of the StoreKit2.