[GH-ISSUE #290] not fully compatible with swift 3 released #171

New issue

Closed

opened 2026-03-03 16:46:20 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 16:46:20 +03:00

Owner

Originally created by @tobatha on GitHub (Oct 11, 2016).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/290

hi,
trying to add the lib via cocoapods, but it'll popup legacy swift version error, and Xcode forces me to upgrade syntax to swift 3

and then i copy all the source folder directly to my project, a lot of compile errors and adjustments need to be done, anyone has the same problem yet?

Originally created by @tobatha on GitHub (Oct 11, 2016). Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/290 hi, trying to add the lib via cocoapods, but it'll popup legacy swift version error, and Xcode forces me to upgrade syntax to swift 3 and then i copy all the source folder directly to my project, a lot of compile errors and adjustments need to be done, anyone has the same problem yet?

kerem

2026-03-03 16:46:20 +03:00

closed this issue
added the
invalid
label

kerem commented

2026-03-03 16:46:22 +03:00

Author

Owner

@tobatha commented on GitHub (Oct 11, 2016):

using carthage, and import the framework solved the problem.

@tobatha commented on GitHub (Oct 11, 2016): using carthage, and import the framework solved the problem.

kerem commented

2026-03-03 16:46:22 +03:00

Author

Owner

@phimage commented on GitHub (Oct 11, 2016):

legacy swift version error, it's a local problem in your workspace
cocoapod and xcode do some dirty things
many times you must go to your Build settings target and choose the swift version
"Use legacy swift language version"
for 2.3 => Yes , for 3.0 => No

@phimage commented on GitHub (Oct 11, 2016): legacy swift version error, it's a local problem in your workspace cocoapod and xcode do some dirty things many times you must go to your Build settings target and choose the swift version "Use legacy swift language version" for 2.3 => Yes , for 3.0 => No

kerem referenced this issue

2026-03-03 16:49:22 +03:00

[PR #172] [CLOSED] Add a fix for a bug with issue number #171 #547