leveldb-library is installed as a dependency of Firebase/Core 4.2.0. When I go to build my project I get three errors from the pod.
I have looked around and leveldb is maintained by Google with the current version sitting at 1.20. The pod leveldb-library is currently at 1.18.3. I'm not sure if Google needs to update the pod leveldb-library, or if Firebase needs to change their dependencies.
Until then, I'm going to use Firebase/Code version 4.0.2 which still builds and runs fine. Let me know if there's any other information you need.
Related
Since the tns-plugin-firebase update to version 15. When doing sidekick cloud builds I receive the message:
Unable to find a specification for Firebase/Core -> 5.5
I followed the intructions fron the community which basically tells to do pods repo update, I even rm -rf the .cocoapods folder and reinstall it.
When building locally it works, but when doing cloud builds with sidekick I received the abve mentioned message.
Is possibl that the pods repo update has to be done in the sidekick server too?, because if not I don´t have a clue why this is happening!!!
Thanks for ideas or hints.
Javier
The issue is indeed related to the Sidekick cloud build service. The pods management is done entirely on the cloud machines, even when you build from a macOS system.
Having said that, the pod is now updated to the latest available version and after a couple of hours (time needed to propagate the changes to the entire infrastructure), you should no longer experience the "Unable to find a specification for Firebase/Core -> 5.5" error while building for iOS in the cloud.
Does anyone know what version of node is used by meteor galaxy?
I just tried to deploy and got the following error:
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
Therefore I assume that an old version of node is used.
The same code worked fine a couple of days ago.
Each version of Meteor is linked to a given version of Node. Galaxy probably uses the one linked to your project. You can see which version it is by running meteor node --version within your project directory (on your local computer), and (potentially) update it by running meteor update.
I am learning meteor to build an app. I am finding things pretty unstable with Meteor. I am using Ubuntu 14.04 and Meteor 1.0.3
Everything is working fine and I had finished couple of Modules. And Suddenly one day, I get this error:
Can't find npm module 'mailcomposer'. Did you forget to call 'Npm.depends' in package.js within the 'email' package?
I know that 'mailcomposer' package is not there and installed it and worked well.
And again, projects work fine and again one day suddenly I get this error:
Cannot find module 'fibers'.
I really want to know what is happening. I have not removed any module nor did I add one. My project was running fine, but later when I opened the system I got the error. Does meteor remove or update modules automatically in the backend? Rather than fixing these errors, I want to know why modules are suddenly being removed.
I am novice in Meteor, apologies if the question is stupid.
I had this issue when I was deploying an Meteor app on Digital Ocean, for some reason I had to reinstall nodejs and fibers package to make it work again.
Are you switching from 1 node version to another?
If you are on the server:
get meteor's node version meteor node -v
verify if the server is using the same node version by node -v
Let me know...
I have suddenly started getting the following message - all seems to work but i don't know why im getting it / what it really means for my app.
The only thing i can think of is that some smart-package im using is looking for an older version of meteor, and mrt is clever enough to not use a meteor version that will break it?
Stand back while Meteorite does its thing
Done installing smart packages
Ok, everything's ready. Here comes Meteor!
=> Running Meteor from a checkout -- overrides project version (0.6.2)
The thing is i'm pretty sure i want to be running on 0.6.2 not overriding it to some other version.
So what does this mean really? - and what do i need to do to not get it.
Thanks
I'm not too sure why it uses that odd terminology. Version 0.6.0 introduced project versions, so each project could run its own version of meteor similar to how meteorite does with smart.json
What Running Meteor from a checkout -- overrides project version (0.6.2) means is this version is overridden by the version in your smart.json. Typically the latest version on the master branch on github (which is checked out hence the wording). So at this moment if you ran mrt it would use 0.6.2.1
I'm sure over time meteorite will eventually be folded into meteor. 0.6.0 was just released a short while ago so some updates still need to be done to make them work better together.
I'm developing a Tool using Symfony 2. Since my Version of Symfony is a bit old, I would like to update. My current installation is the one "with vandors" and I'm using it under Win7 with XAMPP.
I feel somehow stupid, but even after searching the internet for over an hour, I didn't figure out how to update correctly to Version .15
You would be a great help, if you could give me some dumb-secure instructions on this, because all I've done so far to install or patch software was running an exe-file.
Hopefully my english was good enough to point out what my problem is, but nethertheless I excuse myself for all mistakes.
Greetings GrimReaper1908
The update steps are always given in the release announcement (see Symfony 2.0.15 released):
If you already have a project based on the Symfony Standard Edition
2.0.x, you can easily upgrade to 2.0.15 by getting the new deps and deps.lock files. Then, run the vendors script (it also clears your cache):
./bin/vendors install
If you modified deps file to include additional vendors you'll have to manually merge it with the latest Symfony one.
Vendors script requires git client to work. You'll have to install it.
Since you're on windows: Symfony2 installing vendors in Windows