Child Item

API 2 support for iOS 9.3

Bill P.12

What is the timeline for API 2 Swift supporting iOS 9.3?

Find more posts tagged with

API

Abuse

Comments

Greg-DB

I believe the SwiftyDropbox SDK should work on iOS 9.3. Are you seeing any issues, beside the one reported in your other thread? If so, please let us know the details so we can look into it.

Bill P.12

There are a couple of changes in 9.3 that impacted the SwiftyDropbox SDK:

type alias replaced by associated type
Selector format changed
Curried function declaration syntax will be removed in a future version of Swift; use a single parameter list

I have made the changes for 1 & 2 and will live with the warnings for 3.

The removeFolderMember from my other thread was a problem before 9.3. This is a higher priority for me than the 9.3 changes.

Another quick question - will the Swift API ever compile for tvOS without changes. Because tvOS does not support WebKit, I had to add a condition to ignore the WebKit code for tvOS. Not a high priority but thought I'd ask. Thanks.

Greg-DB

Thanks for the additional information! It sounds like you're referring to changes in Swift 2.2 in particular. If you've already made the changes, feel free to submit a pull request. Otherwise, we'll look into it too.

Also, I can't make any promises regarding tvOS support, but I'll be sure to pass this along as a feature request.

Dennis B.20

I'm glad to see that SwiftyDropbox works out of the box in Swift 3.0. But why does it require iOS 10? I can write an app in Swift 3.0 and run it as far back as iOS 8.4 (the oldest simulator on my system) in Xcode 8.

Greg-DB

Hi Dennis, SwiftyDropbox supports iOS 9+, not just iOS 10. You can find the requirements in the README here:

https://github.com/dropbox/SwiftyDropbox

(Also, the Swift 2.3 branch supports iOS 8+.)

Dennis B.20

When I added SwiftyDropbox to my iOS project and tried to run the app I was getting runtime errors that mentioned iOS 10. My project's deployment target was 8.x. I changed it to 10.0 and it ran fine. I see that the framework's deployment target is set to 10.0 when I open its Xcode project so I fired off my inquiry. But dropping it into a new project with its deployment target set to 8.0 runs without problems. Maybe it's because this was on my work Mac instead of my personal Mac. The other theory I'll need to check is whether it's because the failure was in a project that is part of a workspace.