unit tests don't need APPLICATION_EXTENSION_API_ONLY set to yes; in fact, doing so causes this compiler warning in Xcode 9:
ld: warning: linking against a dylib which is not safe for use in application extensions: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphonesimulator/libswiftXCTest.dylib
* swift-3.0:
Update .travis.yml
[Travis] disable pod linting for watchOS 2 configuration
Set Test Host deployment target to 8.0
Update project for Xcode 8 GM
Enums with lowercase
Adapted naming of enums according to swift 3 rules.
Updates for Xcode beta 4
Update for Xcode beta 2
Updated for Swift 3.0
When embedding this project directly into another Xcode project in a target that:
• Is being built for a platform that has a simulator/device dichotomy (iOS, tvOS, watchOS), and
• Is inside a parent project building a Debug configuration
You will get one of two kinds of errors:
• Either the framework module itself is missing at the 'import' level, or
• Some or all of the framework's public symbols can't be found
The solution is to disable ONLY_ACTIVE_ARCH, which will ensure that both processor architectures are built and the symbols can be found.
The main project file was still based on the Project Structure before
the addition of Cocoapods support. It has now been restored, such that
the project can be opened and compiled
* 'master' of https://github.com/matthewpalmer/Locksmith:
Fixed trying to decode the response object for non-read requests
Create License.markdown
Conflicts:
Locksmith.xcodeproj/project.xcworkspace/xcuserdata/matthewpalmer.xcuserdatad/UserInterfaceState.xcuserstate
Evan Maloney
Alexander Belyavskiy
matthewpalmer
Federico Trimboli
Pascal Freiburghaus
Jens Eickmeyer
Tom Brow
Charles Gamble
Herman Olsson
Tai Heng
Niels van Hoorn
Juan Wellington Moreno
Lars Lockefeer
Michael Hahn