Remote Logcat - FAQ
Debugging an app that's running in an emulator, or connected to your development machine is easy-peasy. But, we all know that dreaded phonecall from the client, saying that the app suddenly doesn't work on 'his' phone, but you can't see anything wrong at your end. Oh, if only you could run a "adb logcat" on his phone, but he's miles away!.
That's where remote logcat comes in, just add a few lines of code into your app, and then you can have your app send all it's diagnostic information up to this website, and you can use it to help reproduce what went wrong on the client's phone.
But what happens if I have thousands of users?
If you've got lots of users of your app, then the logs can get pretty chaotic, this is why, we've added the concept of "channels" which is where you can set a separate channel for each user, so that you can filter the logs to a specific user.
How long are these logs kept for?
For free users, we keep 1000 rows per user, the oldest being deleted, for paid users we keep them indefinitely.
Is my data private?
For free users, data is public, so don't post passwords or personal info to the log. For paid users, we make the data private, so only you can see it. - although it's still not a great idea to ever store passwords in any log!. Paid users can also download their data to process it offline.
How do I get started?
Create an account on this website, and you'll get an API key. Once you've done that, add add a few lines of code into your android app, whenever you want to log an event. Run your app, and then come back here to see your populated logs.
That's great but does it do x, y, or z?
We're keeping this system as simple and easy as possible, but if you have a great idea, then send it to us, and we'll consider it.