LocoKit doesn't build on Xcode 9.3 about locokit HOT 9 CLOSED

It sounds like your pods cache has got itself confused.

Those errors look like what would happen if you used outdated dependencies, so I'd try deleting the Pods folder then doing a pod update to force CocoaPods to get the latest of everything.

That should fix it.

from locokit.

Wow, thank you very much for the quick reply!

I just did, on this order:

• On Xcode, cleaned the project and its build folder
• pod cache clean --all
• rm -r Pods/
• pod update
• pod install

Then tried to build it again. It still gives me the same errors (and same amount of errors on each project). I'm puzzled.

I'm running Xcode Version 9.3 (9E145), trying to build for an (actual) iPhone 7 Plus on iOS 11.3

from locokit.

I tried changing the build target to "Generic iOS device" and now I'm getting No such module 'SwiftNotes' on LocoKit Demo App, but still the same 57 errors on my project.

Changed the build target to "iPhone 6s Plus (simulator)" and I'm back to the 20 build errors on LocoKit Demo App and 57 errors on mine.

Changed the build target to "iPhone X (simulator)" and still the same 20 build errors on LocoKit Demo App and 57 errors on mine.

I tried using pod try LocoKit but it says "failed to find project ArcKit Demo App". (off-topic: also, there are broken links on the documentation still pointing to ArcKit on ActivityTypeClassifier. I didn't check others)

from locokit.

I re-did the same steps as before, but this time without pod install at the end. It worked on the Demo App. I'm currently testing the LocoKit Demo App on my iPhone.

My own project (up-until now, an Objective-C only project) still has the same problems as before, though, and the build errors are not even on your project, all of them are on "GRDB.swift"... but maybe you've had these problems before and might be able to help me?

It still fails when I remove the LocalStore, though with 21 errors on LocoKit:

• Instance member 'betweener' cannot be used on type 'Merge'
• 'restartTheUpdateTimer' is inaccessible due to 'private' protection level
  And other similar errors

from locokit.

I'm sorry to bother you, this workaround fixed the problem.

# Workaround Cocoapods to force usage of Swift 4 on all pods
post_install do |installer|
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['SWIFT_VERSION'] = '4'
        end
    end
end

You may close the issue, and I hope other people who see this find it helpful. Thanks for your help.

from locokit.

Hm. Modifying the Podfile shouldn't be necessary. There should be an easier fix.

Have a look in your main project's Build Settings for Swift Version. That value should be inherited automatically by each pod, when CocoaPods generates the workspace.

from locokit.

Also I'm not sure if you can mix Swift 4.0 pods with Swift 4.1 pods. The latest LocoKit (v5.1) is built for Swift 4.1. If you're mixing and matching with Swift 4.0 pods, then you're better to pin to LocoKit 5.0 until the other pods update.

from locokit.

You were right. Swift Version was 3.0 on my main project's Build Settings. I changed it to 4.1, removed the workaround from my pod file, executed pod update again, reopened Xcode, cleaned my build folder and then tried to run my project. It worked.

However, I have never edited this parameter on my project. The project was created with Swift Version 3.0 by default. I created it on February 15th, 2018. Shouldn't Xcode have automatically generated my project with Swift 4.0?

Also, according to the linked StackOverflow question, it is possible to mix pods of very different versions using that workaround (which sets different Swift versions for each pod according to their name), as long as the Swift version is still supported by Xcode (e.g.: Swift 1.0 is no longer supported).

from locokit.

Yeah, that sounds a bit of a mystery. It really should've been set to Swift 4.0 by default, you'd think.

The mixing of Swift versions is interesting! Back in the transition from Swift 3 to Swift 4, it wasn't possible. Nice to know it's at least doable now!

from locokit.