Carthage errors "No tagged versions found for github" - carthage

I want to use Carthage in my projects, so I installed Carthage. I prepared a Cartfile in the project's root folder. When I typed the carthage update command in the terminal, I got this error:
*** Cloning HanekeSwift
No tagged versions found for github "Haneke/HanekeSwift"
The Cartfile file contains these lines:
github "Alamofire/Alamofire" >= 1.2
github "Haneke/HanekeSwift"
Why am I getting this error?

If the project has no tags, then you need to give it a branch or a ref.
github "Haneke/HanekeSwift" "master"
For instance.

Even when specifying the specific branch or ref, Carthage (before 0.17.1) required that the repository has at least one semantic version tag, e.g.:
git tag 0.1
git push --tags
See the carthage documentation for details on how version numbers are interpreted: https://github.com/Carthage/Carthage#tag-stable-releases

Related

How to install unofficial Firebase extension

Looking for information on steps to install the unofficial firestore-nlp-extension, link below.
https://github.com/FirebaseExtended/firestore-nlp-extension
I read the firestore docs but did not see instructions to install a "custom" extension.
Any help is appreciated!
You need to install the extension from a local source but this was available during the alpha and the below link is no longer working
https://firebase.google.com/docs/extensions/alpha/install-extensions_community#install
The specific extension does not seem to be available on the Firebase system:
Error: The extension reference
'firebase/firestore-natural-language-processing#latest' doesn't exist.
This could happen for two reasons: -The publisher ID 'firebase'
doesn't exist or could be misspelled -The name of the extension
version 'firestore-natural-language-processing#latest' doesn't exist
or could be misspelled
For the current beta from the cli tool I found the following:
First, clone the git repo of the extension:
git clone git#github.com:FirebaseExtended/firestore-nlp-extension.git
then run the following commands to build the project:
cd firestore-nlp-extension/functions
yarn add -D rimraf
yarn build
cd ../..
and then to install this extension, run:
firebase ext:install ./firestore-nlp-extension --project=YOUR_PROJECT
if you get a path error you might need to find the right path such as:
firebase ext:install ./firestore-nlp-extension/functions --project=YOUR_PROJECT

Force Swift Package Manager to honour Package.resolved

I am trying to use Swift Package manager to update my dependencies locally to match those in the Package.resolved file.
For example, when I update my dependencies I run swift package update, which updates the Package.resolved file, which I then commit. When I pull this new commit on to a computer that has an existing .build directory with the old versions of the dependencies I would like to update the local versions to the one in Package.resolved.
I was expecting swift package resolve to do this, but instead it updates the Package.resolved according to the .build/dependencies-state.json.
The obvious solution is to delete the .build directory, but this means the dependencies are recompiled every time, which can be slow on CI.
I want the equivalent of bundle install, yarn install, or carthage boostrap. Is this possible?
This has been confirmed to be a bug, and I have opened a bug in the Swift JIRA.

Reinstall Active Meteor Project

Background
I suddenly started getting a Meteor error:
~/.meteor/packages/meteor-tool/.1.4.0-1.1b1o7uq++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/bin/darwin-x64-v8-4.5/fibers.node is missing. Try reinstalling node-fibers?`
After extensive searching, I came to the conclusion that there isn't a known, straight-forward solution to this problem.
Possible Solution
I created a new Meteor project and that works. This is because it is at the latest version of Meteor, and fibers.node is properly installed in the 1.6 (latest version) directory.
The best solution looks to be removing my live project directory and recreating it with the same name (at Meteor's latest version) and then retrieving all the packages, settings and files (HTML, JS, CSS)
Question
What is the best way to do this so that:
I preserve all the packages that I have installed (there are many)
I preserve all the custom settings that have changed from default
I am able to bring all my files (I am assuming this will be simple copy of *.html, *.css and *.js from the original project)
I was able to resolve the error:
~/.meteor/packages/meteor-tool/.1.4.0-1.1b1o7uq++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/bin/darwin-x64-v8-4.5/fibers.node is missing. Try reinstalling node-fibers?
so did not need to go down the reinstalling project path.
I followed the steps in the accepted answer on this thread:
How can I completely uninstall and then reinstall Meteor.js?
Specifically:
mv .meteor .meteor.bak
sudo rm /usr/local/bin/meteor
sudo chown -R $(whoami) ~/.npm/
curl https://install.meteor.com/ | sh
meteor --version -> This will pull the required package for the version your project is at.

Installing Cordova plugin to meteor project using a github tarball link

I'm trying to install a package to my meteor project using a repository in github.
The only way Meteor allow me to install it is using a "tarball" specific link like this:
https://github.com/Wizcorp/phonegap-facebook-plugin/tarball/d8b0f6935a7c6e586188bf85f9da88a1c160790b
Although, the package version referenced in the link is not the one I need (I got that link from an old support post).
Could someone explain me how to obtain that type of link (tarball) from this repository and version (0.12.0)?
https://github.com/Wizcorp/phonegap-facebook-plugin/releases/tag/v0.12.0
So far I have tried:
Copy the tar.gz download link of the right version and running:
meteor add cordova:com.phonegap.plugins.facebookconnect#https://github.com/aogilvie/phonegap-facebook-plugin/archive/0.6.0.tar.gz
Result: "Meteor requires either an exact version, a Git URL with a SHA
reference"
Installing it using the version number:
meteor add cordova:com.phonegap.plugins.facebookconnect#0.12.0
Result: I got "Package installed" but when run ios-device I got the error:
"Failed to fetch plugin com.phonegap.plugins.facebookconnect#0.12.0 via registry".
Downloading the zip file, unzip and put folder in packages folder.
Result: Is not working because is not a package.js inside the folder.
Thanks in advance
You are actually trying to add a Cordova plugin (meteor add cordova:...), not a Meteor package.
Therefore, your trial 3 (local package / plugin) needs a similar meteor add cordova:your-plugin-name#file://packages/folder-to-local-cordova-plugin instead of a meteor add package-name (which will look for a package.js file).
Trial 2 (version number) works only for published plugins.
You should stick with your trial 1 but you have to specify the commit hash (git endpoint + # + commit hash) instead of the tarball link:
meteor add cordova:com.phonegap.plugins.facebookconnect#https://github.com/Wizcorp/phonegap-facebook-plugin.git#c0f8da97a1d65397ada73e958dafed3aeef2e491
See Meteor Guide > Build > Mobile > Native features with Cordova plugins > Installing plugins > Installing a plugin from Git

RealmSwift and Swift 2.1 (module file was created by older version of compiler)

I searched and got answers on using CocoaPods but really i couldn't manage to use it because i didn't what they mean
1- Install CocoaPods 0.39.0 or later. -> i did install it using sudo command
"I stopped here, didn't know what to do"
2- In your Podfile, add use_frameworks! and pod 'RealmSwift' to your main and test targets.
3- From the command line, run pod install.
4- Use the .xcworkspace file generated by CocoaPods to work on your project!
sorry my question looks bad but it is my first time to ask a question here :)
Your list of steps is correct, and assuming CocoaPods installed correctly, you will then need to navigate to the directory of your .xcodeproj file.
In that directory, you can run the command pod init which will create a .podfile in the directory.
You can then continue onto steps 2-4.
However, as of writing this response, Realm's current release doesn't support Swift 2.1. We are actively working on an update for 2.1, which you can follow on this Github Issue.

Resources