I got the same issue. You can work around it in your Podfile by adding this.
But it would be nice if the project file was updated.

# Force swift 3 config
post_install do |installer|
  installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
          config.build_settings['SWIFT_VERSION'] = '3.0'
      end
  end
end

from easytipview.

My steps:

1. Open existing Swift 2.2 project
2. Use the migration tool in Xcode 8 (only on my code, not on the pods)
3. Be frustrated by the migration tool and Xcode in general
4. pod install
5. build project
6. Error message as described

It wasn't only EasyTipView, it happened for Material as well (https://github.com/CosmicMind/Material).

from easytipview.

Hey guys, can you walk me through your problem? I keep on getting this issue from several people but for me it does not reproduce.

Steps I followed:

1. Create a new Xcode project.
2. run pod init
3. add pod 'EasyTipView', '~> 1.0.2' to the Podfile
4. run pod install
5. open *.xcworkspace and import the library where you want to use it.

It all worked seamlessly for me. Maybe it's something related to the way you're migrating from Swift 2.x to 3.x?

from easytipview.

Getting this same error too :/

from easytipview.

When I use the following code I get:

# Force swift 3 config post_install do |installer| installer.pods_project.targets.each do |target| target.build_configurations.each do |config| config.build_settings['SWIFT_VERSION'] = '3.0' end end end

Module file was created by a new version of the compiler... error. Not sure how to get around this.

from easytipview.

If the fix is on the framework's side, then you're welcome to open a PR with the fixes.

from easytipview.

This is still an issue?

from easytipview.

Some people use this to get around your issue:

# Force swift 3 config
post_install do |installer|
  installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
          config.build_settings['SWIFT_VERSION'] = '3.0'
      end
  end
end

I cannot find anything wrong on the library's side, it works with a brand new Swift 3 project, but when you have a Swift 2.x project which you migrate to Swift 3 using Xcode, somehow the pod gets messed up. Maybe this is an issue concerning cocoapods?

from easytipview.

Still looking at this regarding fixes (literally investigating right now).

Is 1.0.2 the latest?

On 31 October 2016 at 13:24, Teodor Patraş [email protected] wrote:

Some people use this to get around your issue:

Force swift 3 config

post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['SWIFT_VERSION'] = '3.0'
end
end
end

I cannot find anything wrong on the library's side, it works with a brand
new Swift 3 project, but when you have a Swift 2.x project which you
migrate to Swift 3 using Xcode, somehow the pod gets messed up. Maybe this
is an issue concerning cocoapods?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#61 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB04RoWeMcvUxNTbq3v3t-T5Ks8aN8ZWks5q5ewYgaJpZM4KW2f1
.

from easytipview.

Yes, 1.0.2 is the latest. If you find something on how to fix this problem from the library's side, you can open a PR.

from easytipview.

When using the force swift 3 workaround - Xcode complains saying the module was created by a newer version of the compiler.

from easytipview.