Take Your Search Game to the Next Level with Dropbox Dash 🚀✨ Curious how it works? Ask us here!
Forum Discussion
What's the actual issue with Apple FileProviders API
I'm trying to reply to this post
https://www.dropboxforum.com/discussions/101001016/dropbox-on-file-provider-support-for-macos-questions/781551/replies/783389
but in a dropbox fashion "Replies have been turned off for this discussion":
billgdbx can you explain exactly what is the exact issue with the Apple FileProvider API for a software engineer? What exactly does "download-on-demand" mean compared to the download now button I see in macOS finder?
When I briefly read the API docs, it seems like the API should be enough; however, I've read many blog posts mentioning that the problem lies with Apple and not with Dropbox/Google/Microsoft. All these posts are blanket statements without any technical details. I'm looking for the hardcore facts, not opinions.
I want to know whether I should consider ditching apple? Or dropbox?
If there is an issue at apple's side - I want to know what it actually is so I can make my own decisions rather than being treated like an idiot and a fool. In my experience, dropbox announces all breaking changes to customer as ultimatums without any true explanation. Now that I think about it... it is actually coming from disrespect and even contempt to your customers.
5 Replies
Walter Hi, thanks for your reply. Yes, I am familiar with the link you’ve provided.
However, they are not of much use to me, as I am looking for an answer from a software engineer who could explain the source of the issue.
I suspect that the semantics of the file provider API and limiting and not good enough from what I’ve read online; however, I seem to miss something major.- Walter
Dropbox Staff
I see, thanks for clarifying that for me yaronhb
In that case, you might be better off asking in the API section or even in Apple's forums.
Whoops I completely missed this reply. Need to make sure I have notifications for this post on
- Walter
Hi there yaronhb - thanks for messaging the Community today.
Let me check with the team on this and we'll get back to you as soon as we have an update.
As for the discussion you were trying to reply to, note that it was closed due to inactivity since there were no comments for more than 6 months now.
In the meantime, please let me know if you're already familiar with the changes outlined here and if you have anything else to add or ask.
Thanks!
