Code Signing issue with Dollar

[bevbomb]

I've had no issues with this before until the newest swift update, i've been uploading this project with this framework to the store with the same configuration for months now

[ankurp]

If its urgent can you try importing using submodule That way you will have more control over the signing by dragging the xcode project into your own workspace or project.

I will take a look at the code signing issue by publishing it to AppStore

[donnywals]

I have the same Issue and I imported Dollar by using it as a submodule..

[bevbomb]

I've always had it as a sub module and never had issues until now, I'm guessing the new Xcode might have left traces of a developers existing code signing, I just haven't at a change to look at it yet to see if there's duplicates

[donnywals]

I have solved my problems. Instead of using a submodule to include Dollar I've installed through Cocoapods. The Dollar.o file disappeared and my app is in TestFlight as we speak!

[ankurp]

I have added code sign to the project. Can someone try with Carthage again using latest code from master d029477

[tsuharesu]

Tried with the latest version of master (using Carthage) and still problematic

[bevbomb]

The only way I've managed to get this working is to use cocoa pods and use_frameworks!

[tsuharesu]

Any updates on this?

[ankurp]

This is something hard for me to replicate as it doesn't throw the same error for me for code signing as I am the person making the library and also publishing the app. This happens only when publishing the app so someone with expertise in this might be able to help out. If someone know the configuration that works for all I am willing to try that.

[tsuharesu]

You could try using the same config as Alamofire? I don't know if it is already equals
https://github.com/Alamofire/Alamofire/blob/master/Alamofire.xcodeproj/project.pbxproj

[simonyangme]

I've opened a PR fixing this issue. It's a problem with including code in the copy bundle resources build phase.