I am using Crashlytics in my android app. In one especial case I handle one exception as non fatal exception. so I used CrashlyticsCore.getInstance().logException(e); and CrashlyticsCore.getInstance().log(""); and it is work fine but it has one little problem . it is not real time . I mean it needs to relaunch the app . how can I see logs message in the exact time?
Related
In my app when some services of it are running it suddenly displays that message on some occasions, but most of the time they work properly, when I've tested them I haven't had any problem.
I'd like to know if its possible to associate the event that causes that message to appear, with giving some extra information or at the very least writing a log that at least shows which class and what line of code causes the error.
From there I could investigate with greater ease what makes that message to appear, as right now I've no clue.
I'd like to know if its possible to associate the event that causes that message to appear, with giving some extra information or at the very least writing a log that at least shows which class and what line of code causes the error.
Every time that dialog appears, a Java stack trace is written to LogCat automatically. You can use Android Studio or other development tools to examine LogCat.
I've integrated Firebase Crashlytics into my app as per Googles instructions:
https://firebase.google.com/docs/crashlytics/get-started
My problem is when I try to do custom logging such as:
Crashlytics.log("testing");
Crashlytics.log(Log.ERROR, TAG, "testing");
Crashlytics.getInstance().crash();
In Firebase Console I get the crash stack callback (as expected) BUT only one (probably the first) log entry from the first Crashlytics.log call done (not the ones above however).
I've waited 48h to see if there's a delay but nothing appears.
It works fine when I "force" the crash in the emulator.
I also tried new RuntimeException() instead of Crashlytics.getInstance().crash()
I am calling the Crashlytics functions in a library which is included in my app(s).
Mike from Firebase here. Crashlytics prioritizes capturing crashes over writing custom keys or logs as crashes are more important to capture. Once a crash happens, we need to act as quickly as possible to get the exact state of the device and all the threads running. Things are still changing and happening after a crash, so to get the most accurate stack trace, if a key or log has not been written out, we will drop that and capture the crash instead.
Given that the log you're not seeing is happening just before the crash occurs, I would expect the log closest to the crash to be ignored. When using custom logs and keys, it's best to log them as early as you can, for example when an activity changes. As a side note, for non-test crashes, this is usually not an issue since you don't know in advance where the crash will occur in your app.
My application is basically a File Manager with junk cleaner. It is working fine everywhere but when i restart my phone Unfortunately app has stopped message appears several times. Also sometimes it appears when any other application is started. Can anyone tell why it is happening, or how to detect the cause behind it.
To detect the cause behind, you can monitor the logcat.
Since the crash occurs after the phone restart and so if you are not able to see the exception in log cat, you can log the same into a file to see the cause of exception.
Use the below link for how to log unhandled exception into file.
https://derivedcode.wordpress.com/2015/06/29/how-to-log-un-handled-exceptions-in-android/
I am new to android and my application involves lot of internet access and many times when the data that needs to come from a web service is unavailable my application crashes.
I tried to avoid as many cases as possible, but i am not sure if my application is crash free.
I am using an application named "delight circle" and sometimes that application crashes and shows me this Toast:
"The application has crashed and a report is sent to the admin"
and takes me back to the previous activity or previous action, and from here i can use the application normally again.
I have 2 questions:
How to make the application work normally after it crashes once. In my application, if it crashes then it asks me for force close and when i click it, it takes me to the previous activity(or action) but nothing works there, if i try to do anything it asks for force close again, i eventually end up force closing the application from Settings --> Applications --> myApp --> foce close.
How to send a report about what actually caused the application to crash?? Right now i have a lot of logs in every activity so, now if it crashes i can find out the exact reason and solve. But when i release the application how can i do this?
Thank You
You have to use UnCaughtExceptionHandler for this.
Here is a example,
http://trivedihardik.wordpress.com/2011/08/20/how-to-avoid-force-close-error-in-android/
Once you override the Exception Handler, you will be provided with access to the Log and from where, either you can send the error log which you get the from the SatckTrace as an Email or use Apis to do it.
I can give an answer to your second question, that is "How to send a report about what actually caused the application to crash" Try Crittercism in your code. It will help you to find the exact cause of failing the application. Not only that, it has so many features, like Live Stats, Unresolved crashes, Crash alarms and more.
My clients using my application on ANDROID and a lot of them are reporting uncaught exception error while using my Flex 4.6 application with latest Flash Player 11.1 swc.
My Flex application uses standard SPARK and MX components. The uncaught exception occurs immediately after application is launched, however none of my functions (connecting to RTMP, RTMFP & socket servers) seem to cause it, the error occurs after all the functions that I call upon program start have successfully executed.
Looks like error code #2063 means "Error attempting to execute IME command.".
My code doesn't call or access any IME functions at all.
It seems that this developer is experiencing same issue and is unable to locate the solution or workaround:
Flex/Flash runtime error #2063 on android
Also, none of the clients using Windows/Mac/Linux are experiencing this issue, only Android clients.
And they all are accessing same application/same code/exact same file.
It also seems like clients are not doing anything specific that triggers this error - they just start my flash site on their android browser and do not do any interaction with it, and getting this error just after launch.
What do I do / what is the best work around for this issue?
And I obviously don't have a stack trace, because my users are using it DO NOT use Adobe Flash Player debugger, however this person and posts seem to be exactly same issue and they have stack trace: http://forums.adobe.com/message/3410527
I have also submitted this issue to Adobe BugBase: https://bugbase.adobe.com/index.cfm?event=bug&id=3101786.
Thanks
can you add to your code the UncaughtErrorEvent.UNCAUGHT_ERROR listener on the main movie loaderInfo object? If you can then it should intercept this error and you can collect some information about it or just ignore it if it doesn't break your application.
best regards