When you have to debug using Logcat for Android

When you are trying to debug Android apps and need to find small string in that huge spam logcat is giving you...

While merging colleagues code...
Because Android studio log cat sucks donkey balls 😂

I never knew you could call the notice of a process being killed "an obituary":

!rant

I was playing with adb logcat some apps and I saw some sensitive info from my bank app. So I decided to go deeper , I saw my entire banking information , WHAT THE FUCK? I feel unsafe now using this bank.

Btw this bank is using react native and forgot to obscured their code in production

android development is shitty af, it will make you super zombie computer nerd that sit on his chair for fking several hours just to find the where the fk is null pointer exception is coming from not only this but for all kind of errors,logcat looks like someone just hacking nasa, you know what im the one who is shitty af i would have opt web dev instead of android dev , this retarded studio and emulator takes too much time to just load a simple fking thing & if i make some change in it i've to install that application again ,it's so pathetic and horse shit thing i've ever encountered , kotlin is fun it's actually great language most of the features are so helpful in it,but the google codelabs,it's all documentation , adding dependencies whole concepts are trash imo, why can't we install the dependencies using terminal what's problem in that ,but no they chose the hard way for no fuking reason, i've successfully wasted a year learning this shitty tech stack, hopefully this NY i will choose different stack , will work till ass off .gonna build some cool projects and will eventually try for internships and all. done with android dev, idk how senior dev's are alive in this field

Android studio logact decided not show any logs today. FUCK YOU.

Trying to debug an app for twenty minutes, and wondering why it was crashing and not logging anything strange.
Realising only after some compulsive head scratching that logcat has been filtered the whole time

When you're too lazy to check of null exception cause

if (mVar != null)

Android Crash is Fucking Bullshit Ever on this Earth Planet.
I really Hate these Number of Versions and Bullshit Incompatibility between each one.

It is Just a Shit Developed on Java.

The Crash Really Fucks the eyes of Developer.

And Fucking Bullshit Errors are not Even visible, Sometimes the shit goes so worst that it does'nt even give the Line Number where error Exists.

Worst OS Developed for Mobile on This Planet.

Anyone getting into these development i suggest IONIC is Best to start instead of Coding Native Bullshit Android.

If anyone knows how to see the realtime errors besides Logcat and Firebase Error please let me know.

Is there anything worse than bugs that you can reproduce easy but lack exception/error messages so you can't fix it?

I'm working on a hobby project for Android and I can't solve a bug and it's killing me (the whole project depend on it). I went through all phases:

1. I notice the bug early but couldnt reproduce it so I let it be.
2. I notice it happen a lot when I started to use the framework for real. Decided now that I need to fix it.
3. Found the exact way to reproduce it.
4. Trying different ways to fix it, nothing works.
5. Write question on stack overflow, no answers.
6. ???

It feels like if you can reproduce the bug 100% of the time it should be easy to fix right? Well hell no - no exceptions, no error message and adb hangs until I stop the procedur. The last kick in the balls? When I stop the procedur I get all logcat messages back and everything look like normal. Just give me a damn error message! Tell me what you're doing or what I'm doing wrong!

I spent three days looking for an error that caused my app to not displaying the layout (the app still was running but it was a black screen). On the third day, i discovered that when I register a SensorEventListener I have to cast the listener to SensorEventListener, otherwise it wont load, or even show errors on the logcat.

Fuuuuu I tried sideloading the devrant app on my Android watch but it kept crashing so I did a logcat over ADB and saw they use function that don't work on watches. So Damm sad I wanted to watch some rants way more sneaky

What afraid me the most...

Test the project thru my phone then this Mrs. Red Lines appeared!!!!

Freaking hell, why google fucking sign in not working after the app is on google play, I have tried everything, run the release app on device and everything works, I thought they are using the bundles to generate and sign the apks so learned everything about fucking bundling and generated app bundles and signed it and generated .apks file locally “I already used the release key not debug key” double checked Auth api keys and installed on device and fucking everything works on the device except if I upload to google play then download to device the middle finger is waiting and google sign in not fucking working, I moved on and attached the app to Logcat and after a lot of digging I saw the fucking error 12501, I went to sleep after seeing this fucking error number. I’m fucking traveling now.

AS logcat

Sqlite.sqliteexception:no such column:Timestamp (code1):,while compiling : SELECT * FROM NOTEs ORDER BY Timestamp

I am trying to get the date and time on each entry of note..

Not exactly a function in a programming language, but as far as Android SDK goes, typing "adb lolcat" instead of "adb logcat" is easier on fingers, and funnier !