I am unaware of any deprecation of the entire tool. The help page clearly states:WARNING: In the future, some features in this tool may be removed in favor of using user approved, high level UI to install configuration profiles. Clients should instead use the Profiles System Preferences pane to install configuration profiles.

You've had six years to plan migration activities accordingly. Another 3 weeks ain't gonna matter much. Just wait.

LOL!nonsense...perfectly appropriate...but...an unnecessary exercise in pain...notoriously fragile... not very portable.. and subject to macOS security blocks.

Just so you know, AppleScript is designed for end users. If you are distributing software, I strongly recommend a lower-level interface. You could use the scripting bridge from native code. Or you could construct AppleEvents manually. That would give you more flexibility to target multiple variants of an app and handle the inevitable errors.

It sounds like you need to use one of the lower-level methods that allows an options parameter that you can set to zero. There is an option for NSDirectoryEnumerationSkipsPackageDescendants that is probably being set as the defeault.

Sorry, but that's a non-starter.

That's C++. I'm surprised it even compiled in the first place. You can try changing the file extension to ".mm" so that you have bona-fide Objective-C++ code.I don't know if that will help. I have no idea if modern C++ std code is compatible with block captures. This is the kind of thing where you would have to have detailed knowledge of the standard, detailed knowledge of how it is implemented in this particular library, and detailed knowledge of how this particular clang compiler handles this particular object in a block context. In other words, it is high risk and you really shouldn't attempt it.Also, I don't think code like "@(p->c_str());" is going to work. If you want to work in Objective-C, just use Objective-C. Don't add any C++ unless you have no other choice, such as if you depend on a one-of-a-kind C++ library. And these days, pretty much everyone is using Swift. I have no doubt that Apple will continue to support Objective-C, but avoiding Swift is a career-limiting move.

There is a reason for that lack of detail. 😉

Uses can choose any file for wallpaper, so you will have to find some other way to do it. I think what you will have to do is take over setting of the wallpaper. Your app should be able to do that. The user will have to set the desktop wallpaper using your app. Then you can do whatever it is you were planning, and then set the desktop yourself.

Ttry adding some ASCII colour escape codes and see if they work. I doubt they will.

Has anybody encountered a 'push' problem within Xcode and resolved the problem?And resolved the problem? You are setting the bar pretty high there aren't you? Out of pure laziness, I do sometimes still use Xcode to push, but that is getting more and more rare. Xcode is still useful for comparing changes. Just today I found the context menu option that does blame, I think. But I don't trust Xcode for git operations. It takes extra work to avoid Xcode bugs.

Do you think this would be enough?I don't work for Apple. Only App Review can approve an app. You didn't quote the exact comment from Apple and I don't know anything about your app, so it is difficult to say more than just quote Apple's guidelines. However, I can tell you that your app is in a "RED FLAG" area. It is going to be under intense scrutiny by Apple. This is one of the top scam areas and avenues for illegal apps. I will assume that you are an honest developer. Imagine how someone might use your app for gambling, drug dealing, file sharing, money exchange, prostitution and *** trafficing, and a host of other scams that I don't even know about. How would you prevent that activity? Or is your app designed to facilitate it? Don't bother trying to explain it to me. As I said before, I don't work for Apple. You have to demonstrate, to Apple, with your app (your words are meaningless), that you are an honest developer who does not want that kind of activity.

I strongly suggest avoiding using a custom setup program. If you have components that need to be installed in system locations and/or need to run as root, then use the Apple-provided installer. You would distribute your app as an installer package. But only do this if you absolutely have to. And please include an easy way for users to remove all of the parts later. And double-check that whatever you are uninstalling, can be uninstalled by your uninstaller. For example, Apple recently introduced System Extensions that can only be uninstalled by dragging an app to the trash. But in most cases, apps installed using an installer package cannot be uninstalled by dragging an app to the trash. Of course, none of this is allowed in the Mac App Store. If at all possible, distribute via the Mac App Store. You might find a lot of developers complaining on the internet about it and Apple 30% fee. Ignore them. Use the Mac App Store!

Let's see what the App Store Review Guidelines say:Apps with user-generated content present particular challenges, ranging from intellectual property infringement to anonymous bullying. To prevent abuse, apps with user-generated content or social networking services must include:A method for filtering objectionable material from being posted to the appA mechanism to report offensive content and timely responses to concernsThe ability to block abusive users from the servicePublished contact information so users can easily reach youI guess that means yes.

I don't know if this is something that you even have access to. The only thing you can check is NSHomeDirectory(). There is no guarantee that the filesystem of the home directory is the same as the rest of the device. On the Mac, for example, they are different.You might be able to use IOKit to get the size of the underlying device. I have done this on a Mac, but not on iOS. Generally Apple doesn't want people (developers) knowing how much RAM or storage is available on the device.Apple does support methods to manage storage, such as volumeAvailableCapacityForImportantUsageKey and volumeAvailableCapacityForOpportunisticUsageKey.