Prerequisites:
Xcode Version 7.2.1 (7C1002)
CocoaPods 0.39.0
pod 'JWPlayer-SDK', :inhibit_warnings => true
When I set Debug Information Format to Dwarf the warnings disappear
But it's only necessary for the JWPlayer SDK, so please fix it.
while processing
/Users/wojtek/iOS/myproject/Pods/JWPlayer-SDK/libJWPlayer-iOS-SDK.a(JWPictureInPictureHandler.o):
warning:
/var/folders/53/y97w7fr55sjc262qprp8lby80000gn/C/org.llvm.clang.jenkins/ModuleCache/P0EAZ51IY1Y2/Foundation-3DFYNEBRQSXST.pcm:
No such file or directory while processing
/Users/wojtek/iOS/myproject/Pods/JWPlayer-SDK/libJWPlayer-iOS-SDK.a(JWPictureInPictureHandler.o):
warning:
/var/folders/53/y97w7fr55sjc262qprp8lby80000gn/C/org.llvm.clang.jenkins/ModuleCache/P0EAZ51IY1Y2/Foundation-3DFYNEBRQSXST.pcm:
No object file for requested architecture while processing
/Users/wojtek/iOS/myproject/Pods/JWPlayer-SDK/libJWPlayer-iOS-SDK.a(JWPictureInPictureHandler.o):
warning:
/var/folders/53/y97w7fr55sjc262qprp8lby80000gn/C/org.llvm.clang.jenkins/ModuleCache/P0EAZ51IY1Y2/AVKit-95365SBJXV2.pcm:
No such file or directory
Podlock doesn't give me a version number, but I include the pod like this :
pod 'JWPlayer-SDK'
According to CocoaPods page it's JWPlayer-SDK 2.1.0 (https://cocoapods.org/pods/JWPlayer-SDK)
Related
After Firebase configuration, I try to run the simulator IOS 15.2 on iPhone 8 with visual Studio code with the command "run without debugging" but I get this error :
Launching lib/main.dart on iPhone 8 in debug mode... CocoaPods' output:
Error output from CocoaPods: Ignoring ffi-1.14.2 because its extensions are not built.
Try: gem pristine ffi --version 1.14.2
[!] Automatically assigning platform `iOS` with version `9.0` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.
Error running pod install Error launching application on iPhone 8.
Exited (sigterm)
and when I run the error suggestion :
ismac#ismails-MacBook-Pro flutter_chat % gem pristine ffi --version 1.14.2
Ignoring ffi-1.14.2 because its extensions are not built. Try: gem pristine ffi --version 1.14.2
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions for the /Library/Ruby/Gems/2.6.0 directory.
Can you please help me ?
This is the solution that worked for me.
follow this video : https://www.youtube.com/watch?v=EXp0gq9kGxI
then open Podfile in ios folder and change :
"# platform :ios, '9.0'" to "platform :ios, 'current_version_of_ios'"
current_version_of_ios : is the real version of IOS in the moment you read this solution then before run the simulator :
Delete the podfile.lock file from iOS folder after that go to ios folder and run a below command
Pod install
It will install all the packages which are in your podfile.
Also, you need to set the target platform. Stay in the iOS folder and run below command
open Runner.xcworkspace
then your app will be open in XCode. Click on the "Runner" and set your target platform to 8.0. I fix my iOS build issue using this hope this will work for you.
I'm attempting to compile a Xcode .xcworkspace built by Unity that contains Google Firebase. I tried all the solutions I could find online without any luck. If you have any ideas I can try, can you please share?
The error I'm getting is that it can't find the BoringSSL-GRPC library. I tried running pod update and pod install to resolve this and I can see while it does successfully install BoringSSL-GRPC (0.0.7), Xcode still gives this error even if I open the .xcworkspace file.
ld: library not found for -lBoringSSL-GRPC
When I add use_frameworks! to the podfile per a suggestion online, I get this error:
ld: framework not found FBLPromises
When I removed the above and then add use_modular_headers! per another suggestion, I get this error:
fatal error: module map file '/Users/xxx/Documents/Builds/DemoProj/Pods/Headers/Private/grpc/gRPC-Core.modulemap' not found
Each time, I changed the podfile, I'd run pod update and pod install before doing a clean build in Xcode.
Here are the versions I'm using:
macOS Catalina 10.15.6
Unity 2019.4.4f1
Firebase 6.15.2
Xcode 11.6 (11E708)
CocoaPods 1.9.3
And here is my podfile:
use_frameworks!
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '10.0'
target 'UnityFramework' do
pod 'Firebase/Core', '6.24.0'
pod 'Firebase/Analytics', '6.24.0'
pod 'Firebase/RemoteConfig', '6.24.0'
pod 'FirebaseCrashlytics', '4.1.0'
pod 'FirebaseFirestore', '1.15.0'
end
Notes:
I've also tried adding ,:modular_headers => true at the end of each pod which didn't work.
I have a paid developer account and Xcode is configured for that account
When I try the normal way through Cocoapods:
# Uncomment the next line to define a global platform for your project
platform :osx, '10.13'
target '1072 Scouting' do
# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!
pod 'Google/SignIn'
# Pods for scouting1072-mac
end
I get the error:
[!] The platform of the target `1072 Scouting` (macOS 10.13) is not compatible with `Google/SignIn (3.1.0)`, which does not support `osx`.
How would I install Google Sign-In so I can have similar functionality to an install on an iOS project?
Old Cocoapods Configuration
I am using Xcode 7 Beta 4. Initially I was using Cocoapods version 0.38.2 and when I ran pod install --verbose in Terminal it said it downloaded dependencies for Bolts, FBSDKCoreKit, FBSDKLoginKit, FBSDKShareKit, FBSDKMessengerShareKit, and Pods for iOS 8.1. With this setup my app compiled successfully. Below is the Podfile and Objective-C Bridging File that I used to import the Facebook SDK (so Swift recognises its referenced methods and Objective-C classes). Note that the specific versions shown in my Podfile are also the versions that get installed even if I do not explicitly specify them at the time of this writing.
Podfile
xcodeproj '/Users/<my_username>/MyApp/MyApp.xcodeproj'
pod "FBSDKCoreKit", "~> 4.7.0";
pod "FBSDKLoginKit", "~> 4.7.0";
pod "FBSDKShareKit", "~> 4.7.0";
pod "FBSDKMessengerShareKit", "~> 1.3.1";
MyAppObjCBridging.h
#ifndef MyAppObjCBridging_h
#define MyAppObjCBridging_h
#import <FBSDKCoreKit/FBSDKCoreKit.h>
#import <FBSDKLoginKit/FBSDKLoginKit.h>
#import <FBSDKMessengerShareKit/FBSDKMessengerShareKit.h>
#import <FBSDKShareKit/FBSDKShareKit.h>
#endif
Problems encountered when updating to Cocoapods v0.39.0 (from v0.38.2)
The console showed the message "CocoaPods 0.39.0 is available. To update use: gem install cocoapods. Until we reach version 1.0 the features of CocoaPods can and will change. We strongly recommend that you use the latest version at all times.", so I installed the this latest version of Cocoapods 0.39.0 by executing sudo gem install cocoapods in Terminal.
But when I compiled my app it gave me the following errors:
/Users//MyApp/MyApp/MyAppObjCBridging.h:14:9: 'FBSDKCoreKit/FBSDKCoreKit.h' file not found
In Xcode I "Product > Clean" (CMD+SHIFT+K), but this did not make any difference. So I ran sudo gem uninstall cocoapods in Terminal (which listed 0.38.2 and 0.39.0 as the versions that were currently installed) and selected version 0.39.0 from the list to uninstall the latest version and revert back to 0.38.2. I then ran pod install --verbose. When I tried to compile my app it compiled successfully and ran in Simulator again.
Question 1
Why does it give the error that it can't find "FBSDKCoreKit/FBSDKCoreKit.h" when I use Cocoapods version 0.39.0 instead of the older version 0.38.2?
Question 2
If when using Cocoapods version 0.38.2 (the version that compiles with my app) I decided to add platform :ios, '9.0' to the first line of my Podfile (above its existing contents) and run pod install --verbose in Terminal, the Terminal messages tell me that it installs each pod target for iOS 9.0 (instead of iOS 8.1) (i.e. - Installing targetFBSDKCoreKitiOS 9.0).
When I then run my app it successfully compiles and opens in Simulator and displays some new warnings associated with iOS9, most of which I understand. However I do not understand why this one appears. Why is this warning appearing?:
ld: warning: directory not found for option '-L/Users/Ls/code/swift/FreeWifiSearch/FreeWifiSearch/build/Debug-iphoneos'
Question 3
When using Cocoapods version 0.38.2 (the version that compiles with my app), if I decided to add use_frameworks! to the first line of my Podfile, and platform :ios, '9.0' to the second line of my Podfile (above its existing contents), and then run pod install --verbose in Terminal, the Terminal messages tell me that it installs each pod target for iOS 9.0 (instead of iOS 8.1).
When I then run my app the following errors appear:
Use of unresolved identifier 'FBSDKLoginButton'
Use of unresolved identifier 'FBSDKLoginManager'
Use of unresolved identifier 'FBSDKLoginBehaviour'
Why does adding use_frameworks! to the top of my Podfile prevent me from using the Facebook SDK identifiers? (noting that when I don't have use_frameworks! at the top of my Podfile my app successfully compiles and runs in Xcode Simulator, and I can successfully retrieve a Facebook SDK Access Token and login to Facebook)
Since posting the original questions the following was performed and resulted in no compiler errors:
Updated from Xcode 7 Beta 4 to Xcode 7.1.1 by downloading latest from App Store
Added use_frameworks! and platform :ios, '9.0' to top of Podfile
Changed deployment target to iOS 9.0: Project Settings > Targets > General > Deployment Info > Deployment Target > 9.0
Updated CocoaPods to v0.39 with sudo gem install cocoapods
Reinstalled pods with pod update --verbose
Added import FBSDKLoginKit above the class containing Facebook SDK methods
Performed Clean (Shift+CMD+K) and Run (CMD+R) in Xcode to test on device
Add "${PODS_ROOT}/Headers/Public/FBSDKCoreKit/FBSDKCoreKit" in your target's Header Search Paths in Build Settings
For me it's OK now(CocoaPods 0.39, FBSDK 4.10)
I try to migrate my existing Apple Watch app to watchos2 but fail to get realm.io running on the watchkit extension.
The Realm documentation describes how to get everything running with Swift 2.0:
use_frameworks!
pod 'Realm', :git => 'https://github.com/realm/realm-cocoa.git', :branch => 'swift-2.0'
pod 'RealmSwift', :git => 'https://github.com/realm/realm-cocoa.git', :branch => 'swift-2.0'
And on Realm news from end of June it was mentioned that watchos support is on the way with Pull Request 2139. It seems that changes in this PR are not merged into any branch.
When I run the watchkit extension with the swift-2.0 branch I get the following error:
dyld: Library not loaded: #rpath/Realm.framework/Realm
....
Reason: no suitable image found. Did find:
/.../DerivedData/Build/Products/Debug-iphonesimulator/Realm.framework/Realm: mach-o, but wrong architecture
Are there any plans to merge the watchos2 support soon and make it accessible? Or are there other recommendations or resources to get Realm running on the Apple Watch?
What versions of Xcode and CocoaPods are you using? I believe that CocoaPods actually needs some unreleased functionality to work completely with watchOS 2 apps, see https://github.com/CocoaPods/CocoaPods/pull/4004, which will be included in the upcoming 0.39 release.