-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swift 3 build errors #65
Comments
I'm sorry, there was a problem with merge. I'll fix it later today. |
No problem at all 👍 |
@malcommac It seems like Swift 3 branch is broken. I still cannot use the branch in pod and I can see so many differences to the base implementation of the Swift3 Branch. We have 2 options here:
I think Swift 3.0 GM is upon us and a working Swift 3.0 compatible code base is only reasonable. |
@malcommac I'm also still getting the same errors on the swift3 branch. |
I thought I could get away with an easy rebase. I prayed to Linus to make it so. But here I am, 45 minutes in, with no end in sight. I would strongly suggest option 2 that @mohpor suggested. |
@robbiet480 😆 😆 You had me at ehem, The conversion should be straight forward. 😎 |
Built a new Swift 3 branch off of the latest master, available here. |
Merged in swift-3 branch. |
I am trying out this framework for my future project (it looks great), but unfortunately the test project I have started (Using Cocoapods (1.1.0.beta 1) with:
doesn't build. There is two different type of errors and 15 errors overall:
RegionHandlerStateDidChange
,RegionHandlerStateDidChange
,RegionHandlerError
, ...Beacon
has two declarations. One inBeaconManager.swift
and the other one inCommon.swift
I'm guessing you are testing and building your project without the pods (have you used
pod lib create ...
?) This is always error prone.Could you take a look. I'm lost a bit. There are files in my pod that have not been added to your test project. 😖
The text was updated successfully, but these errors were encountered: