I have an Android app out there in the market. It uses Flurry, and it reports these crashes relatively often. I could never reproduce it, and since there's no stack trace, I don't even have any idea what code triggers it. Is anyone familiar with this issue?
Update: 2 years later, I'm still getting this crash pretty often.
Related
Off late I am getting these strange crashes on some of the users devices. As per the stacktrace, the code which crashed wasn't even supposed to be executed.
at <package>.ProfileFragmentKt$navigationItemSelected$drawerListenerForLogout$1$onDrawerClosed$1.onClick$lambda-1(ProfileFragmentKt.java:430)
at <package>.OveralLeaderBoard$$InternalSyntheticLambda$1$02abf2b02b6613054134ac54a51b1d4fe0a610803b5aa4ed543d8bcfe4103eb0$0.onChanged$bridge(OveralLeaderBoard.java:2)
at androidx.lifecycle.LiveData.considerNotify(LiveData.java:133)
at androidx.lifecycle.LiveData.dispatchingValue(LiveData.java:151)
at androidx.lifecycle.LiveData.setValue(LiveData.java:309)
at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:50)
OveralLeaderBoard screen has nothing to do with ProfileFragmentKt.
I have never seen this InternalSyntheticLambda, .onChanged$bridge before. You won't even find it in the class kotlin bytecode.
Can anybody tell me what this is? And how to solve it?
I had the exact same problem in the Crashlytics console of an app in production.
I managed to reproduce the crash on my phone: there were no mention of the totally unrelated fragment in my crash logs.
If fixed the crash, and there were really no reason why this unrelated fragment should be mentionned here.
So I can't explain why, but my advice would be to ignore the unrelated fragment to anyone facing this issue.
I'm getting a lot of crashes on this in my production application. I have not been able to reproduce it myself, and the crash stack trace does not mention any of my own files. As you can see on the crash overview, I get the same crash many different places.
Is this a bug in the bottom navigation library? Has anyone else experienced this?
My application sometimes crashes on some devices, with this error:
IndexOutOfBoundsException: Inconsistency detected
After some changes and spend a couple of hours, not sure if it fixed or not.
I read some of the answers and did what they say .like this post and this.
But how do I sure if the changes are working while I don't know when the exceptions occur?
How to create a situation that leads to the exception?
I know this could be a very ambiguous question But I need some help. I'm working for a project which consists of users doing some tests in Tablets. the tests they do are always the same but sometimes the app crashes for certain Tablets/users. As I mentioned, the tests are the same for every person and the tablets too. However, in some cases the app stops working. I have looked for some Warning errors ( intent receiver leaked , etc) but I think I have resolved them. I think this could be a matter of memory problems (mp3, images are in the tests).
Is there a way of testing this app's stability? I must mention that these crashes only happen when there are some users doing this in the same Wi-Fi and the same SERVER. Could be a server problem?
Thank you for the help.
Check out Crittercism or something similar - I have found it to be VERY useful in the past.
It will send a crash report for you, providing the stack trace.
(yes, there are plenty of others that may be better / worse / different / the same etc... I'm just mentioning this one because it is the one I had experience with)
My app had been chugging along fine on the Android market until last night when it was reported a customer found an error. The customer must have downloaded the latest version of the app because he tried to use it again with the latest version and the error came back.
I looked at the stack trace of the error and found it was caused by a NullPointerException when passing information between two activities, namely with the onActivityResult() method.
I checked the code and can't find what could have caused the error. I tried to figure out what steps the user took to get the error, but found nothing wrong, on the emulator Android 1.6 /Android 2.2 and my own phone (Android 2.2). I couldn't find any problems no matte rhow much I tried to crash the system.
Another thing that is strange is that the particular onActivityResult method is called a lot in my app. So it is odd that only one user has reported problems.
Also, it says the user's platform is "OTHER". I don't know what device that could be.
So my questions are:
1) Could this problem be an issue with the user's device and not my application?
2)What to do when you cannot find the cause of a crash?
1) Yes, they may have a custom ROM; they're known for doing things like this.
2) Unless you can reproduce it, you [probably] can't fix it.
Can you contact this customer? If not, there may be nothing you can do.