I'm trying to follow the instruction for Linphone, to download the SDK for iOS, either here:
https://wiki.linphone.org/xwiki/wiki/public/view/Lib/Getting%20started/iOS/
or here: https://gitlab.linphone.org/BC/public/linphone-iphone
They both start with this CocoaPods thing, that im not familiar with, and it doesn't seem to work... all I get is this error:
[!] Couldn't determine repo type for URL: 'https://gitlab.linphone.org/BC/public/podspec.git': (<unknown>): mapping values are not allowed in this context at line 3 column 17
Tried on Mac M1, and Intel Mac. Always the same error. I would rather not build the entire SDK, just need to include the SDK in my project.
To include the sdk you need to place a source to their podspec git in the pods file and then you can use it as if it was in cocoapods
Example ios pod file:
source ‘https://gitlab.linphone.org/BC/public/podspec.git’
source ‘https://github.com/CocoaPods/Specs.git’
platform :ios, ‘11.0’target ‘test’ do
project ‘test.xcodeproj’
pod ‘linphone-sdk’, ‘~> 5.0’
end
This is fixed for iOS since some months.
I have forgotten to fix this also for MacOS podspec repo.
This is now also fixed.
The explanation is here : https://github.com/BelledonneCommunications/linphone-sdk/issues/207
TL;DR : It was an issue caused by Gitlab's way to handle files not found (redirection) for Cocoapods-version.yml, confusing Cocoapods.
Related
I just downloaded XCode 12.2 and created new empty project.
Then I imported Parse SDK with pod.
The problem is that the project doesn't build.
errors found:
framework not found Parse
ld: framework not found Parse
clang: error: linker command failed with exit code 1 (use -v to see invocation)
How can I solve it?
I was having a similar issue and tried a dozen different fixes. The one that seemingly worked was to update the Podfile to install Parse directly from GitHub.
I changed pod 'Parse' to pod 'Parse', :git => 'https://github.com/parse-community/Parse-SDK-iOS-OSX.git'
I say "Seemingly" because some of my other fixes may have contributed to its success.
Which version of the Parse SDK are you using? Can you share the contents of your Podfile?
Did you open the xcworkspace file instead of the xcodeproj?
I just installed Parse 1.18.0 using Cocoapods and it is working normally.
I have a issue, regarding Xcode, in react-native permission file
in which GeneratedInfoPlistDotEnv.h file is not found.
How to fix this?
Already changed Info.plist Preprocessor Prefix File to
${CONFIGURATION_BUILD_DIR}/GeneratedInfoPlistDotEnv.h
but it did not solve.
issue is:
:1:10: fatal error:
'/Users/DAMAGE/Library/Developer/Xcode/DerivedData/EmployWise-fzbhiywasjfdjnfqjsfnxjbhahzs/Build/Products/GeneratedInfoPlistDotEnv.h'
file not found
Was getting this from react-native-config cocoapod. But its been fixed in v1.4.11. Was due to the older version not writing output script variables, which XCode 14 requires
This issue comes when react native is not able to link to the configuration file like .env file created in your react native environment. If you have used any react native config framework like react-native-config. then make sure this framework is linked for your iOS environment as shown below
react-native link react-native-config
If you are using react-native version >= 0.60 then follow the below steps after linking is done.
Go to ios folder and run pod install.
Next do the following:
1. Remove Derived Data from Xcode
2. Clean Build Folder
3. Build the project again
I had this problem, my solution was to change the Xcode build system from "Legacy Build System" to "New Build System" in the Workspace Settings under the File menu
In my case, I was trying to add a new target for rn-extensions-share and forgot to add all necessary libraries for that new target.
Having trouble archiving - I receive a Build System Information error that says
Multiple commands produce '.../Library/Developer/Xcode/DerivedData/.../Build/Intermediates.noindex/ArchiveIntermediates/.../IntermediateBuildFilesPath/UninstalledProducts/iphoneos/GoogleUtilities.framework':
1) Target 'GoogleUtilities-00567490' has create directory command with output '.../Library/Developer/Xcode/DerivedData/.../Build/Intermediates.noindex/ArchiveIntermediates/.../IntermediateBuildFilesPath/UninstalledProducts/iphoneos/GoogleUtilities.framework'
2) Target 'GoogleUtilities-ac14cd06' has create directory command with output '.../Library/Developer/Xcode/DerivedData/.../Build/Intermediates.noindex/ArchiveIntermediates/.../IntermediateBuildFilesPath/UninstalledProducts/iphoneos/GoogleUtilities.framework'
I recently updated to the latest version of Xcode (v 10.0). I am also using Cocoapod version 1.6.0.beta.1
Using GoogleMaps pod version 2.7.0, GooglePlaces pod version 2.7.0
When I run 'pod install' it also installs 'GoogleUtilities (5.3.0)'.
I tried deleting my Podlock, Podfile, .xcworkspace, etc and starting over with a new Podfile, pod init, pod install, etc. after updating Cocoapods but still no luck.
I'm looking for a duplicate relating to GoogleUtilities or Places or Maps in Build Phases within Embed Pod Frameworks, but not having much luck. When I look inside the Pods folder, I do see two GoogleUtilities frameworks, "GoogleUtilities-00567490" and "GoogleUtilities-ac14cd06", but both appear not to have the exact same contents.
Only now experiencing this issue after updating Xcode to version 10.0.
For me, the same issue was coming and Most of the people saying to change the build system to legacy, but when I tried its It started swift compilers error. resolved as mentioned below.
Go to your target and click on (your_app_name_target).
Select Build Phases.
Expand Copy Pods Resources.
See the section Output Files.
This section should be empty. Remove any entry there.
Rebuild your Project.
Going to File > Workspace Settings and then changing the Build System from "New Build System (Default)" to "Legacy Build System" will allow you to archive for now. Hopefully, another solution comes along for using those pods and the new build system in Xcode 10.0
I installed this library in my project (a command line tool) via Cocoapods, but, even perfectly following all the instructions, Xcode doesn't see the module even if it's in the same workspace of my program
This is my Podfile:
platform :osx, '10.11.5'
use_frameworks!
target 'my_program' do
#no version required, otherwise it throws an error
pod 'Gloss', :git => 'https://github.com/hkellaway/Gloss.git'
end
and, as said, it installs the library without any error and creates a 'my_program.xcworkspace', which is where I should build the program instead of 'my_program.xcodeproj'. The problem is that I can't import the library in the main source file because Xcode thinks that there is no module named 'Gloss' in the workspace (even if there actually is).
What could I do?
Thanks
EDIT
I discovered that command line tools don't support framework. Thanks, Apple.
Anyway, I won't delete the question so that someone having my same struggle can have a quick answer
Did you build after importing Gloss?
xCode gave me an error saying there was 'no such module' until i built the project and it then detected it.
i just bought the newest imac.
running OS 10.9.5- 64 bit
I am using cocoapods version 0.34.1
xcode latest stable build (6.01)
And for some reason the repo ive been working on for a year now is having all kinds of trouble finding pod header files.
for parse, im getting 'Parse/Parse.h' file not found,
I could be wrong but i dont think its specific to parse.
Nothing is different about my project environment except for the new computer.
If you are using pod 'Parse-IOS' change it to pod 'Parse', '~> 1.4' because has been deprecated.
Also, does it happen for pods to not been found by ProjectTests?
If so, add at the top of the podfile this line:
link_with ['ProjectName', 'ProjectNameTests']
and at your project Build Setting->Other Linker Flags, add $(inherited).
If you dont need the test target, remove it from the build to solve this.
Go to edit scheme under project and expand all the items in the left column. Highlight any references to test and hit the minus button.
This information can save you from banging your head into the wall.