Integrating GoogleCast SDK with Cocoapods - ios

We are having some trouble integrating GoogleCast SDK for iOS v3.3.0 via Cocoapods.
Running 'pod install' installs the pod just fine, and it also builds and runs the project without issue, but when the app launchs on the device, it crashes with this message:
dyld: Library not loaded: #rpath/GoogleCast.framework/GoogleCast
Referenced from: /var/containers/Bundle/Application/735F9E66-D710-4E36-937D-50146F67B4DC/xxx.app/xxx
Reason: image not found
We have researched the subject thoroughly but we're stalled at this point.
Thanks, greetings.

I've tried what you say.
Using an iPhone 6 and cocoapods 1.2.0 seems to be building and running perfectly.
I've made a test here: https://github.com/alextarrago/gcasttestcocoapods

Related

dyld: Library not loaded: #rpath/libswiftCore.dylib after Xcode Update

I am having problems with an app I've been working on for a while. Everything was fine until went mad and updated Xcode to 9.4 (previously 9.3).
I'm using a third party framework compiled on swift 4.0.3. I worked perfectly, but after the update it wouldn't compile (can't build the framework compiled on 4.0.3 with 4.1). I downloaded and installed the Swift 4.0.3 Release Toolchain and i'm able to build with no errors.
However, when I run the target on the device (iOS 9.0 ipad) it crashes with dyld`dyld_fatal_error:
dyld`dyld_fatal_error:
0x1fe9008c <+0>: trap
0x1fe90090 <+4>: nop
The console outputs this:
dyld: Library not loaded: #rpath/libswiftCore.dylib
Referenced from: /private/var/containers/Bundle/Application/2E966F50-67E3-4250-858C-382319CD6274/myApp.app/Frameworks/myFramework.framework/myFramework Reason: Incompatible library version: myFramework requires version
1.0.0 or later, but libswiftCore.dylib provides version 0.0.0
Some Facts:
The Framework is in Embedded Binaries and Linked Frameworks and Libraries under General and Link Binaries with Libraries and Embed Frameworks under Build Phases.
This app need's to deploy on iOS 9.0 and the Deployment target is set accordingly.
I installed Xcode 9.3 again, but I had the same problem using the 4.0.3 toolchain.
My suspicions:
Can the Toolchain be corrupted in some way? I installed Swift 4.0.3 Release 2017-12-05 (a)
Even though I am working with the 4.0 toolchain, I can only choose from 4.1 and 3.3 under Swift Compiler in Build Settings. I imagine this is overwritten, but not sure.
My main concern is that even though the deployment target is set to iOS 9.0, under the BASE SDK is set to 11.3, and can't choose another. I can't find the 9.0 SDK on the internet. Could this be the problem?
Also, all of my certificates are valid and ok.
Thanks in advance, I'll add edits every time I find something new.
Well, I didn't receive any help here, but just in case anyone needs to know, the only way I managed to solve this was asking for an updated version of the framework we are using. It appears this is a compatibility problem that has no solution.
Following #Danf instructions solved for me.

CSYMGenerator Can't Open XCode Project Run

I got
CSYMGenerator cannot be Opened because of a problem
message while running my project.
OS: High Sierra v10.13
XCode: 9.0
Termination Reason: DYLD, [0x1] Library missing
Application Specific Information: dyld: launch, loading dependent
libraries
Dyld Error Message: Library not loaded:
#rpath/CrashlyticsLanguageSupport.framework/Versions/A/CrashlyticsLanguageSupport
Referenced from:
/Applications/Fabric.app/Contents/XPCServices/CSYMGenerator.xpc/Contents/MacOS/CSYMGenerator
Reason: image not found
Crashlytics Version 3.8.3 (120)
Fabric Version 2.6.14 (1285)
I just deleted the Fabric app and this error went away.
According to a post here by Mike Bonnel who works at Google on Crashlytics at Google, Fabric app has not been used in years.
I just ran into the same problem. To get it to work I ran
rm -rf ~/Library/Caches/com.crashlytics.mac
AND I deleted the Fabric app off my computer.
This is not an ideal workaround, but at least I can build and run my app now. This is definitely not ideal, but the issue went away. I was using XCode 8.2.1 on the latest High Sierra.

Conflicting Framework names -- Crashlytics + Fabric

My app crashes whenever I try to build it. It crashes specifically when I change the iOS platform on the Cocoapods. When the Cocoapods platform is iOS 7, I run into no build problems, when I edit the platform to 8.0 I get a build error that tell me there's conflicting frameworks. Specifically the crashlytics and Fabric framework. I can't downgrade cocoapods (unfortunately) so I Was hopging someone could advise me with another to go about this. Please not that I'm not using any swift fraemworks.

dyld_l_fatal_error when Running app on device but not simulator after iOS 9.2.1 update on device

I've been banging my head against the walls with this one. I recently updated my iPhone 6S to iOS 9.2.1 and since then I get the following error:
dyld: Library not loaded: #rpath/AMScrollingNavbar.framework/AMScrollingNavbar
Referenced from: /var/mobile/Containers/Bundle/Application/EB384B23-1BCC-4E23-8FB7-E0349C4F52B9/Qanda.app/Qanda
Reason: image not found
The weird thing is not only is it running on the simulator but AMScrollingNavbar was installed with cocoapods then removed… So it shouldn't even be trying to search for it.
I have tried multiple things non of which have worked:
cleaned the project
restarted xCode
reset the Pods
deleted the App from the device and reinstalled
followed all these steps: https://forums.developer.apple.com/thread/25352
also tried this how to ENABLE_BITCODE in xcode 7?
Thanks!

iOS 9.1 crash due to APAddressBook book (image not found)

I am using APAdressBook cocoapods. I am getting crash on iphone 9.1 version, with this error message:
dyld: Library not loaded: #rpath/APAddressBook.framework/APAddressBook
Referenced from: /var/mobile/Containers/Bundle/Application/5D501E04-C41B-42E8-A0CE-841ADB8A1526/......
Reason: image not found
Finally, I got a solution. To solve this issue, follow these steps:
Firstly remove workspace in your project and pod file.
Update your cocoa pods and system
Reinstall all pods
quit from Xcode and run it again

Resources