Android Crash alert systems? - android

[Disclaimer: I looked around at the other stackexchange websites and couldn't find a perfect place to post this question, so i'll post it here. i'm happy to take it down and place it somewhere else if you know where this is supposed to be. please do not downvote because of that]
Currently we use a 3rd part tool (HockeyApp) for monitoring crash reports on an android app. They have an API that i can use to query for crash reports. I want to be able to have an automated crash report system where if certain conditions are met, i get an email (or maybe a phone call). For example, say i get 9001 crashes within an hour, i would like to receive an alert.
Is there a tool for doing this already? (crash monitoring for android, using hockeyapp is highly preferred)
I looked into rolling out my own Ruby on Rails app for doing this, using ActionMailer apis. has anyone had any experience with this and recommend it? Or what would be a better approach? (If i have to roll out my own tool, dev time is of the essence)
What kind of tools do your/other companies use for this kind of situation (crash alerting/pager duty)?

You can continue to use HockeyApp and set a webhook when a new crash was created. This webhook can point to your own backend or to a service like Zapier, which can then trigger a PagerDuty, email or all kinds of notifications.

You can look at crashlytics. They notify by email and send daily stats on email. For detailed stats you can visit your account. But this service is only for crashreporting.

Related

Send text to app (not specific phone number)

I don't know if this is even possible, couldn't find anything usefull on the internet.
I wanted to make an app, that me and some of my friends could send a message trough "my app" and that everyone who has that app, receive the message, without using a phone number.
So basically, same as WhatsApp GroupConversation, but then without using a phone number.
Is this even possible?
If it is possible, could you put me on the right track to start with.
Hope I am clear enough, if not, tell me :)
Edit:
This just pops up in my head (didn't look on internet yet), but what I want, is a kind of a shoutbox.
This is possible, in fact WhatsApp does not use your phone number for this at all.
You simply provide your phone number to asure a unique ID and proof that you are indeed in possession of this phone with the validation SMS.
From there on, your phone number isn't even used anymore.
You can go 2 ways with this;
Create a simple webservice with a database on which you just save and request messages. Maybe make a little difference between get all or get latest message. Anyone, hooking into the group, can just fetch the same data. With the use of GCM push notifications, you can make this pretty instant.
Use XMPP, which is a chat protocol kinda all the chats use. Whatsapp, Google talk, FB messenger... This will provide you with instant messaging just like any other chat app or program you know.
Option 2 is by far the best in final functionality, but be warned that XMPP is quite complex and error prone.
You can look into the asmack and asmackx libraries for Android, which will give you the basic functionality with ease. Going a bit deeper, you'll have to dig into the protocol and really get to know it though.
ps. For both you'll need your own server, however with asmack(x) you are also allowed to use Google's Talk servers for free. Communication will go through your Gmail account. Basically with this you just make your own version of Google Talk.
It is possible by implementing server-client architecture. Your app will use a common database for all the users. whenever an user install your app, he will achieve an unique user ID. if anyone uninstall it, his id will be destroyed. You can track the users from those ID in database. You don't need phone numbers.

How to implement push notification in Android

i am developing app that would receive data from server any time. i have searched some mechanism to do this
C2DM: but i require Google account for each device on which app will be installed
MQTT: but it is a Third party and a person for which i am developing does not trust third party because he says in future may be that third party start charging for their service or even stop their service.
Pooling: which is again not a good idea because it consume lot of battery
Is there any better way of doing this..
i have posted similar question before but did not get a satisfactory answer and i am still confused...
The most straightforward and reliable way to implement this is by using C2DM. Requiring a Google account on each device shouldn't be a big deal, because users need that anyway to access the Android Market. The only major exception to worry about will be Kindle Fire users.
This blog post has a good listing of alternative ways to roll your own push service: http://tokudu.com/2010/how-to-implement-push-notifications-for-android/. However, you need to think if the extra effort (including maintenance) is going to be worthwhile.

capturing and sending logcat output by email or to server

I'm developing an Android app which has some complex logic and I am having issues troubleshooting the app that has been installed by beta-testers.
Does anyone know if there's an easy way to capture logcat output and either manually or automatically email it back, or send it to a server? I have asked the person testing the app to install aLogcat app and send me the log, but there are 2 issues with this:
it sends all kinds of logging from other apps that I'm not intested
in
it captures a limited amount of log entries, and did not give the
log entries I needed.
If anyone has any experience with a similar problem and how to solve this, it would be much appreciated.
You could use Acra. I have used and it is great. It can send the crashreport to a GDoc.
I'm pretty sure there are other tools too, and I think since Android 2.2 google has something built-in but I haven't found any docs about it. (Android Error reports).
I would recommend Bugfender. It lets you send all logs to a centralized cloud server, completely managed by you, no need for the user to intervene.
Note: I am one of the creators of Bugfender, still I think this could help solve question.

Notification in Android

I am trying to create an android application which allows users to receive updates from a particular server/website.
For example, whenever I have a piece of information I want to share, like an update or notice, I will post it on this website. Whenever, there are updates posted by me, I want the phone to receive a notification about it as well and add the information into the app.
Just like the gmail app on android. Update immediately when there is a mail and not have a timer to check at every interval.
Does anyone know how can I go about it? I am new to programming, it will be good if your answers in steps for me to follow. Thanks in advance.
EDIT:
The android application will have a login page which is define the type of the user. Only the updates and information regarding the type of the user will be pushed.
However users of this application, may not login with a google account.
You could use C2DM - Cloud 2 Device Messaging. It's relatively new tech though so not a lot of resources about it.
Here's a good tutorial on it: http://www.vogella.de/articles/AndroidCloudToDeviceMessaging/article.html
Edit: PS: and it's in beta too so might work best as a proof of concept more than an actual product.

Bad sides of C2dM

We all know that as of Android 2.2 a push notification system exists (C2dM). However, I do not see many developers using it.
In my next project I plan (hope so) to use this system. So before I dig into it, I would like to know what are the bad sides of it? Why people do not use it?
It can't be just because of incompatibility with systems older that 2.2.
Nice question. Here is my 2 cents :
C2DM is still in beta
There is a limit on the number of messages you can send. If you need to send a large number of messages, then you need to explain it to Google and get it approved.
The device must have Android market with one google account signed in.
The documentation is a bit flaky [My personal opinion]. e.g. The signup form asks for the app package name and the ROLE account ID on the same page providing wrong impression that once signed up, the package name is bound to the ROLE account ID and can only receive messages from it.
I don't think people are not using it. Rather I find most developers are very much interested in it and are implementing it. My C2DM post has the most visitors of all my posts.
However the problem might be for individual developers who develop stand alone apps. They may be reluctant to use it since they will require to maintain a server side component to push messages.
[Will update my ans. if I find anything else.]
I think a lot don't use it because
They have no real need for it
So far it isn't very straight forward
Stated above, it is in beta still.
With Apple Push, it is pretty straight forward (on the device side), you simply invoke a call and it gives you the device token. With C2DM, you have to (though you can dig for the google account) prompt the user for the google account, then you have to hope they don't have too many Apps already registered for C2DM (100 limit now).
Server side, I'd say C2DM is a lot easier than push, you simply are invoking a service, with APNS you need to setup pipes, use certificates, etc. It isn't easy for most to do. C2DM is just invoking a HTTP call. The server aspect adds a bit of expense as well, hosting application services isn't always cheap.
I don't see a lot of Apps having the need for it, so far Twitter and Facebook seem to be (Though they may be using something else, I am not sure).
And, it is still a beta service. Do developers want to invest a lot of time in a beta service? Not all do, some will take the risks.
I've used it and I like it, I have it coupled with APNS and have had great success so far.

Categories

Resources