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!
Thanks for the request! I'm sending it along.
For reference, I believe it's possible to use a Swift library in an Objective C app, though unfortunately I don't have any instructions for doing so available.
For API v2, we only have a Swift SDK and currently don't have plans to build an Objective-C SDK. As Greg mentioned, you should be able to just use the Swift SDK from your Objective-C code.
For API v1, the iOS SDK is written in Objective-C, and the code can be downloaded from https://www.dropbox.com/developers-v1/core/sdks/ios.
This decision is insane.
Is there any technical justification you can give me that will allow me to convince my PM that our team now has to learn another programming language to use your API? Box, S3, GDrive, OneDrive and iCloud all have Objective-C apis available. Do you really feel that you'll be able to compete for IOS developer mindshare with just a Swift-based API?
I strongly urge you to reconsider.
For those who haven't tried it yet, I just tried and believe that we'll need to expose the Swift classes to Objective-C explicitly by inheriting from NSObject and adding the @objc decorator. (I was able to make some progress just by making the Dropbox class "@objc public class Dropbox : NSObject", but I believe there is more work to do to expose the full functionality.)
We'll try to make sure it's easy to use the Swift SDK from Objective-C code before the Swift SDK is taken out of beta. Please let me know if you have other concerns about using the Swift SDK from your Objective-C projects.
> We'll try to make sure it's easy to use the Swift SDK from Objective-C code before the Swift SDK is taken out of beta.
Nice, I hope you'll come up with something because my knowledge of swift is worse than my french and my french is rather poor.
Back-pedaling here a bit, sorry. After further investigation yesterday, it looks to me like making it easy to call SwiftyDropbox from Objective-C is going to be considerably more work than I thought. I don't think Objective-C support will make it into the initial release of the SDK, but it is something we will look at after the initial release.
We'd welcome contributions from the community here if perhaps someone on this thread is more experienced with mixing Swift and Objective-C than we are. The biggest challenge identified so far is the use of enums.
The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.Sound good? Let's get started.