I am trying to connect my tessel to firebase, and I have tried everything. Is anyone else having a similar problem? I have read that the tessel uses different web sockets than firebase, but I am really new and don't know much about that. Could anyone help me out?
Glad to hear that people are interested in using Firebase with the Tessel. I'm one of the Firebase engineers who has been working with the Tessel folks to make this happen. There are two Tessel Forum posts that give some more detail on the problem:
Firebase cannot be compiled by Colony
Websockets on Tessel
The Firebase node packages uses faye-websockets, which the Tessel compiler couldn't support. We got nodejs-websockets to compile, and built a version of the Firebase library to test the concept. I was able to read and write from Firebase using the Tessel, but we were very hesitant to release a separate version of Firebase to NPM just for use on the Tessel, especially since nodejs-websockets is not as well maintained as faye-websockets. I then spent an evening working with the Tessel folks to get faye-websockets working, and it now compiles, with the changes sitting out on a branch (tessel/runtime/JH-HTTPParser). I don't have a timeframe on these getting merged into Master and being shipped out to production, but I know there are a good number of SSL and websocket based API's who are waiting on these changes to hit the main branch.
TL;DR: Firebase compiles on the Tessel (you can build the code off the above branch), and it can either read or write (not both at the same time). When I get some more time, I will be debugging Tessel + Firebase to get this working correctly.
With the acquisition I haven't had much time to try. Last time I checked, things were compiling and running for some operations (I haven't tested everything) if we used a non-minified version of the Firebase library (not currently provided to end users). The issue here is that the minification puts all the variables in the same line, and the Tessel Lua VM would complain that there were more than 200 variables and wouldn't like it. I can play around with it some over the next week and see where things are, otherwise I can ping Jon and the Tessel folks to see how we can best move this issue along.
I am using SynergyKit for realtime communication. You can download Node.js library, which is fully supported by tessel platform and using websocket library, which is one of few libraries written in pure javascript.
You will be able to live observing all data in collections and sending messages. There is documentation for Node.js.
Related
Our app has been in the Play Market for 4 years.
Before the last build, we added AppMetrica in the app:
implementation 'com.yandex.android:mobmetricalib:3.13.1'
implementation 'com.android.installreferrer:installreferrer:1.1.2'
implementation 'com.yandex.android:mobmetricapushlib:1.5.1'
The project with these instruments was successfully uploaded into the Play Market without any notifications (errors or warnings). In a few weeks after that, I made minor changes in sending reports in the AppMetrica and received the following notification from Google:
"We reviewed XXX, with package name XXX, and found that your app uses software that contains security vulnerabilities for users. Apps with these vulnerabilities can expose user information or damage a user’s device, and may be considered to be in violation of our Malicious Behavior policy.
Below is the list of issues and the corresponding APK versions that were detected in your recent submission. Please migrate your apps to use the updated software as soon as possible and increment the version number of the upgraded APK.
Vulnerability TrustManager You can find more information about TrustManager in this Google Help Center article."
We don't use TrustManager and his classes in the project.
What can be the possible reason for rejecting? Is it possible that this rejection was made by mistake? How can we find out what is the reason for that? Can AppMetrica cause this setback and should we stop using it?
Also, in the rejection text they said you can set up the network config (https://developer.android.com/training/articles/security-config) in the app -- how can it help?
We are fighting this trouble for two weeks and we hope for your help
Being that Meteor on Windows does not currently support Velocity/Jasmine, I would like to use a cloud-based solution for running Meteor with Velocity. But so far I have not had success. I have tried Nitrous, Codeanywhere, Koding, and Cloud9.
I also use the Meteor Windows Preview and the same issue. See my SO: Easiest way to create mobile apps on official Meteor for Windows
I had the additional constraint that I want to compile Mobile Apps which is currently not supported by the Windows Preview.
I've not had success with cloud-based solutions either beyond very basic test apps. The whole chain is just too fragile, there's often something you need to configure that you can't get at in a cloud solution. Basically, your options are:
Vagrant
Dual-boot (thanks #sbking)
Buy a Mac
I would recommend 3 because it will save you time (and therefore money). The first 2 are fiddly, just adding more sys admin work when we should all be coding :)
ALTERNATIVELY
Switch testing tools to Laika. See related SO: Laika vs Velocity on meteor TDD
Laika (apparently) still works for the moment, even though it is no longer officially supported. I will be using it for my current project in the next few weeks.
I'd be really interested to hear what solution you go for.
At the risk of offering you a pocket-knife when you want a power-tool, there is a meteor package, jasmine-green, that does not require Velocity and therefore works well with Cloud9. While this means that you would not have the full capabilities of a velocity-based jasmine or mocha package, it is a lot better than nothing. Just type:
meteor add fongandrew:jasmine-green
It might be a stopgap while you find a better long-run solution.
I need support in SignalR for Android client. I am using following client SignalR/Java-Client but unable to know where to start :) We are completed .net self host & working fine. But only problem with Android & iPhone. Can any one please guide me how to start the next steps for Android & iPhone.
You don't give a lot of details, so it's hard to give a concrete answer, especially since your question is very broad to begin with. Nonetheless, you should have a look at the official samples for the Java client, to get you started. If you have implemented the server side yourselves, and know your Java, it should be pretty easy to figure out from the code provided in these samples. The Java client is, in my experience, very easy to use.
As for an iOS client, a Google search came up with this library. I have never used it, and it looks like it's not getting a whole lot of support, but you could always give it a shot.
My parse powered application for iOS worked great until 2 weeks ago when the users could not connect to my parse databases. I examined the problem and I observed that if I use my IP, I could not access parse APIs but using a USA/UK VPN does the trick without any problem.
I tried my 3G connection, different public WiFIs from the city, nothing worked.
people around the globe can access too, the problem is with IPs from Romania.
Does anyone know about this or a possible fix?
The application is live in appstore so the code and everything is the same as at the time when was fully functional.
UPDATE: I also updated the parse sdk to the latest version, build and tested the app but same problem.
Seems it was a parse temporary error, it's fixed now.
I've had very mixed experiences trying to host on Meteor.com.
I often get "This site is down. Try again later.". Initially I couldn't figure out why, but then I suspected that the problems were caused by me accidentally restoring the "system.users" collection. I tried restoring without that, but the site went down a few days later. Today, it's magically back up again without me doing anything.
"meteor logs" shows nothing. It's a complete black box.
I've investigated other options (Heroku, demeteorizer, meteor bundle, etc), but they are clunky and unreliable too (problems installing fibers, doesn't seem to handle Meteor.call() properly, etc).
I would really like to host in production on Meteor.com, but I feel I can't trust it right now. Free is nice, but I need reliable, production-quality Meteor hosting. When will I be able to buy that from Meteor.com?
Thanks,
Graeme
From the documentation:
We provide this as a free service so you can try Meteor. It is also helpful for quickly putting up internal betas, demos, and so on.
So it means it's intended to try things out, not for production. They offer it for free, I think it would be bad manner to abuse it. And with so many people around trying the thing, don't be surprised if it's overloaded from time to time.
I'm not sure if and when the Meteor team will make this hosting production ready. At this moment, I'm happy they're focusing on making the framework mature.
For other options, Heroku works as a charm. I'm using it for several projects, including production ones, and had no problem. Don't bother with demeteorizer and such. Just create a new app and run these commands (replacing appname with your app name):
heroku git:remote -a appname
heroku config:add ROOT_URL=appname.herokuapp.com
heroku config:set BUILDPACK_URL=https://github.com/oortcloud/heroku-buildpack-meteorite.git
git push -f heroku master
MDG (the Meteor Development Group, the core team) is working on a hosting solution called Galaxy. It will likely tie in to meteor in ways other solutions won't (such as meteor deploy). This will be (AFAIK) a paid service, and as such will likely offer analytics for better insight (my guess). And of course scaling will be taken care of for us.
More on the subject: http://www.meteor.com/blog/2013/10/01/geoff-schmidt-at-devshop-8-getting-meteor-to-10