Unable to find a specification for `KontaktSDK-OLD` depended upon by `BeaconCtrl`

[JpegDev]

After a pod install i had the following: Unable to find a specification for KontaktSDK-OLD depended upon by BeaconCtrl
I think that Kontakt updated their sdk and their pod

[aachojnacki]

Hi,

Thank you for your interest in Beacon Control, and for reporting this issue to us. We’ve already addressed this problem once with Kontakt, and they fixed it by creating the “-OLD” pod. Now it seems they’ve upgraded it. We think this might be a mistake on their side, we’ll look into it and let you know.

On 26 Apr 2016, at 12:40, Jean-philippe Arnaudin notifications@github.com wrote:

After a pod install i had the following: Unable to find a specification for KontaktSDK-OLD depended upon by BeaconCtrl
I think that Kontakt updated their sdk and their pod

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub #2

[JpegDev]

Hi,

Thank you for your answer i disabled the Kontakt.io part for the moment. And it should work till Kontakt did their update.

Have a nice day.

Ps: It is a nice open source project :)

[hugocarlmartin]

Are there any plans on using the new KontaktSDK? Or where are we in this matter?

Did you @JpBeepeers solve this in any way?

Grateful for any news on this.

[engmsaleh]

I have solved it by using this workaround from this answer

Add the following to the end of the podfile

pre_install do |installer|
# workaround for #3289
Pod::Installer::Xcode::TargetValidator.send(:define_method, :verify_no_static_framework_transitive_dependencies) {}
end