We didn't use swift in our app development for iOS devices.
To use API v2 in iOS platform, we need an objective-C version!!!
Please kindly provide an objective-C version!
@Gregory, thanks for the update. I just want to reiterate that for many of us, having any Swift code in our production apps is not an option at the moment and I would urge you to consider shipping a clean Objective-C Dropbox SDK -- not an Objective-C interface to the Swift SDK -- if you want developers to be able to use it.
There is no good reason as to why the SDK should be written in Swift at this point in time. A Swift wrapper around an Objective-C SDK works perfectly without excluding people, whereas the other way around is no good. Please see my previous comments if you need any clarification as to why.
Thanks for the news, also very happy v1 will continue. If I could forward one more positive thought, if/when ya'll do v2 for objC it would be nice if it was an evolution not a revolution
Just curious being a newb - what is in the v2 api functionally that is not in v1 other than oauth2 instead of oauth1? I am actually pretty happy with v1...
Hi TK, we have an overview of what's new in API v2 in the blog post here:
https://blogs.dropbox.com/developers/2015/11/dropbox-api-v2-launches-today/
@Gregory: any word on Datastores deprecation? Any delays there?
Raheel, no updates on that.
We need to keep using the deprecated Sync API, too.
Could you please delay the deprecation of Sync API?
Otherwise, we have no choice to disable Dropbox support but only offer iCloud support in our new apps.
"That unfortunately means it will take us longer than we intended to offer it." -> Does that mean that we will get an Obj.C API at some point?
FWIW after looking I don't really need anything in v2 that badly - I do my own sync and fileid tracking using the rev field and found it pretty easy to integrate...
It might be nice to just see a point release that adds oauth2 to v1...
C. Tim, thanks for the feedback. I'll send this along as a request, but I can't make any promises. Just to clarify a bit though, the Sync SDK itself it built on the Core API and so should continue working, but it's no longer officially supported. The full details are in the blog post.
Joris, yes, we do intend on offering a solution for using API v2 from Objective-C. (And for reference, it is already possible to call the API v2 HTTPS endpoints directly if you want.)
TK, API v1 itself does already support OAuth 2 in addition to OAuth 1. I imagine you're talking about support for OAuth 2 in the SDK though, so I'll send this along as a feature request for that.
Is it possible that you can open source the deprecated Sync SDK so we can maintain or modify it to use Core API v2 by ourself?
C. Tim, I can't make any promises, but I'm sending this along as a request to make it open source.
It is incredible that a company such as Dropbox would even go down this path. Supporting developers should be any companies #1 priority. Instead it sure seems like you and your team are focused on doing 'what you enjoy' instead of supporting the rest of us. Our team has chosen to pull all of our Dropbox support and only support Google Drive. We need a cross-platform way to access and manage files from a variety of devices and the lack of true Obj-C support is ridiculous. The two pages of complaints and explanations on why this is important only results in 'we underestimated, and it's not a priority'. This is an extreme disappointment to us and we feel that only by directing our clients to other services and moving our business away will the point be driven home. I'm sorry for your approach to this and your response so far has only been disappointing. Good luck with your push towards Swift, it sure looks like it's going well for you. I'm glad you get to use the Enums you like.
Very sad to read this thread that goes since August without actual solution for ObjC.
Our app already integrate iCloud and Adobe CC, I was excited about bringing Dropbox to our users but that won't apparently happen soon.
It is a shame.
First I am a developer and NOT a paid DropBox fanboy You know, I felt the same way at first about the lack of a v2 API for objC. However after integrating the v1 SDK for iOS, and taking a ****** look at what "new" or different features are available in the v2 iOS SDK for Swift, there really are no significant features missing.
You are really stressing over the name - v1 vs v2 without considering what the SDK provides or how DropBox really works (under the trappings of any of the SDKs). The core DropBox API is usable by anyone directly using HTTP requests - the interface libraries are just someone's take on making it easier for a given platform or programming language. Furthermore, these libraries (SDKs) are not optimal - NONE of them expose ALL the features of the core DropBox API as it exists as a RESTful interface. They all leave out something you might want or do it in a way which may not fit your desired usage.
What is nice about the DB SDKs is that they are open source and you can enhance them to your liking, use them as is, or roll your own. Also the folks on here are somewhat responsive compared to the other platforms (Drive, iCloud, OneDrive...). The core DB API is much easier to use than any of those other storage APIs as well IMO.
So while I too felt the same way, I have to agree with DropBox - even though they don't say it the iOS v2 SDK does not really bring a lot to the table that the v1 SDK does not bring. And as a developer that has used the v1 SDK, if they were to come out with a v2 SDK for objC, I would be bummed if I had to rewrite a bunch of code for new/different interfaces just to achieve the same functionality I already have today. The only thing I would do to their v1 API is make it Oauth2 compliant and leave everything else the same anyway.
Steve,
My ObjectiveCBridgeable proposal is designed for these sorts of scenarios. It's currently in review, not sure if it will be approved or make Swift 3 but it makes bridging between the two languages a lot easier without sacrificing advanced Swift features.
I open sourced a Dropbox v2 client library I wrote to migrate my app Close-up over to v2 today. It's named TJDropbox, you can check it out on Github here. It's 100% Objective-C and has no dependencies. It only supports a few endpoints for now, but it's easily extensible and may be useful for others! It even allows for migration from the v1 SDK if that's what you're currently using.
I just got an email that the v1 API is now deprecated. SO what are existing iOS applications that use the core v1 API supposed to do? How can you possibly deprecate an API without having a new v2 API for people to use that have coded with objective C? Really?
Hi Gregory,
Could you please share current details and state of DBv2 (swifty).
As per following migration guide for v1 to v2, it says Objective-C SDK is coming out in Aug 2016.
https://blogs.dropbox.com/developers/2016/04/announcing-the-v1-to-v2-migration-guide/
Are you guys planning to release a separate v2 SDK that is purely Objective-C or it's still the Swifty SDK with Objective-C support?
Thanks in advance.
Dropbox Swify, as per today is it usable by existing objc apps?
@Mike K. Ashok M.: The API v2 Obj-C SDK is currently in beta (https://github.com/dropbox/dropbox-sdk-obj-c) pending a few additions, and will be released for production at the end of this week. Thanks for your patience here.
vincy w.: In theory, yes it is, but it would preferable to use our new Obj-C SDK, which will be released for production by the end of this week.
Hi,
It's September and there isn't yet an ObjectiveC version of the SDK.
Any news?
Thank you.
Hi Nicola, the official Objective-C SDK is available at the link in Stephen's post:
https://github.com/dropbox/dropbox-sdk-obj-c
Ok, thank you Gregory
