Wile researching api/frameworks for the backup solution for iOS, I slowly came to realize that there is no effective method for the corporate to monitor/audit file-system on their iOS fleet. Ie - api is there, but limited and the user can always kill your app. Not to mention that you're quite limited in terms of background processing/monitoring Am I missing something?

I have the need to evict local copies of files in swift, currently I'm doing it the naive way: while !evict_ok { do { try FileManager.default.evictUbiquitousItem(at: url) evict_ok = true } catch { sleep(evict_retry_interval) } } this is needed because we might try to evict the item that has not yet finished being uploaded to the drive. ?> Is there a way to register for a notification / get file state which signifies it's being uploaded, when the upload has not been initiated by us (some other filesystem activity)

Is it possible to create a non-sandboxed app for iOS, that will actually install and run, via manual build/sign process? Ie. via xcodebuild/codesign with custom provisioning profile. It seems xcode IDE does not allow to disable sandboxing for iOS apps. App failing the AppStore review is not an issue - do not intend to distribute it.

Is there a way to implement a launchd agent / service to do continuous background monitoring on iOS? The idea is to roll the app on the device once - have it request permissions if necessary and then have it autostart and run in the background, transparently to the user. I understand there are background tasks - but I understand these are limited in terms of time-window they can run and I would still need to make foreground, before I can schedule another? I do not intend to distribute the app/package outside of the org.

Good day. I'm working on a backup-app, that needs to watch a large directory tree on iOS. On macOS we have FSEvents API, which, I understand, is suitable for the task, but not available on iOS. So I opted to try GCD DispatchSource - works, but needs to open descriptors for every watched dir in the tree to receive events. I've hit the open-file limit (256). There's still at least a third option of trying endpoint-security api, but that seems to be a massive overkill. ?> Is there a way to increase the open-file limit for the app? If no - maybe I'm missing some other api to use for the task? I do not need to distribute the app in store.