
Currently using xCode 8. Is there any fix for this? Integrated it by drag dropping the SwiftyJson.swift file in project root

More errors
SwiftyJSON is not Swift 3 ready. Last update is from 3 months ago and for example back then Swift 3 defined private keyword differently. It is yet to be seen if the creators return (bummer, I know)
Damn! :(
For now you can use this fork, it seems to be working well: https://github.com/acegreen/SwiftyJSON/tree/swift3
@fortmarek Cant use that fork if your project is a cocoapod itself because cocoapods does not let you define forks/other repos in a pod spec file, only a single published version.
So this does not work as well: http://stackoverflow.com/questions/20936885/cocoapods-and-github-forks ?
I usually use Carthage, so bear with me.
No, that is referring to a podfile, not a podspec, which is different.
Oh right, OK, so maybe you could implement it manually...?
@kylebrowning I encountered some libraries which supports both of Swift 2.x and Swift 3 version in different branches while it labels different versions in pod packages. It can solve in cocoapods if the owner of the repo handle this.
@ttuygun IM not sure I follow. Im referring to being able to use SwiftyJson siwft 3 version, via cocoapods dependency in a podspec file, not a PodFile
In PODSPEC files (not PodFiles) you cannot define a git branch or a specific Repository. You can only define what is pushed to the specs repo with pod spec push trunk
If you own your own library and depend on this one, there is no way to link to a fork unless the owner of that fork publishes the podspec to trunk.
I dont know how else to explain it.
Read more here, http://stackoverflow.com/questions/22447062/how-do-i-create-a-cocoapods-podspec-that-has-a-dependency-that-exists-outside-of
@fortmarek I am down to implement it manually, but that wont work if people are downloading my library. I cant ask users of my library to implement swiftyJSON themselves, so until the owners of SwiftyJson publish the swift-3 branch to podspec, I have remove the use of SwiftyJSON which is unfortunate.
Closing this one to cleanup the issue list, feel free to reopen this if needed.
Cheers
Most helpful comment
For now you can use this fork, it seems to be working well: https://github.com/acegreen/SwiftyJSON/tree/swift3