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
Related
I have an Android sender app and Android TV receiver app. When I start to connect the Android TV receiver app, it returns an error code 2255 in onSessionStartFailed().
I have referred the Google Cast documentation (https://developers.google.com/android/reference/com/google/android/gms/cast/CastStatusCodes) and cannot found the definition of 2255 in this page.
Also, I try to read the code from com.google.android.gms.cast.CastStatusCodes, it seems that error code 2255 is a special case.
if (var0 < 2300) {
return String.format(Locale.ROOT, "Cast remote display status code %d", var0);
}
Thanks in advance.
Not sure if this is your issue, but this can happen if you try to run the Cast Debug Logger on a non-google receiver hardware.
As it says:
Warning: Make sure to change setEnabled to false for a production receiver.
Properly disabling it in prod fixed the issue for me. But, man, it's so bad that error codes are not properly documented. There are several other that can also be thrown for various reasons that are undocumented.
What was actually happening for me is the CAF library was throwing an exception because it is trying to load the debug logger, but the debug logger is not supported on non-google hardware. This caused the VM to not launch properly and so it started throwing remote display errors.
If that is not your issue, you should try to log in to the back-end if your device if possible and download an error log. Sometimes that can highlight what is happening. I don't know if it's possible to crash the VM in other ways, but it might be and the error log might show why.
Debugging my app, android studio is not catching fatal exceptions and I just get "Your application has closed", and looking at Android monitor, I don't see anything regarding an exception, maybe I see something about Logging event(FE), so maybe by guess is that maybe firebase is catching exceptions which works great for deployed applications, but not for running in debugger.
Can someone tell me how I can keep both deployed exception catching with firebase, but also still allow exceptions to be caught when running in android studio debugger.
In logcat set it to "No filter" (on the left hand side drop down list) and filter by you app package name
This way you can see your logs after the process has stopped
I am developing an android app. My app gets crashed often. I want to save the logcat messages in sd card while the apps gets crashed to find the root cause. Is ther any way to do this?
A few ideas which might help you step toward fully automated crash log gathering. We have yet to roll a full system here, we've had enough luck with just grabbing devices after they've crashed or asking for more info from our QA group, but:
ACRA is relatively easy to implement, and even if you don't implement it, the source is on github for you to poke around in.
The related question Android crash reporting library (pre Froyo) has a number of links and solutions, including android-remote-stacktrace, the aforementioned ACRA, Android-Error-Reporter, and other commercial solutions.
Some devices capture the crash output automatically, you can grab it via adb pull /data/log/dumpstate_app_native.txt.gz or similar -- the paths should appear in logcat. These tend to be overwritten with each crash, though. (If anyone can answer whether this is a manufacturer-specific feature or something that appeared in some version of android's core, I'd love to know!)
You can get a logcat app, e.g. aLogCat or many others, that you can install on your device.
TestFlight is going into beta on Android side; they have crash reporting on the iOS side and should on the Android side too, and there are various other lovely benefits to using their services -- and integration is really easy in our experience.
If you're rolling your own inside your app, you need the READ_LOGS and WRITE_EXTERNAL_STORAGE manifest permissions (even for local builds), then you can use the logging API or a regular File.copy or even a system call off to logcat itself. There are a bunch of options and examples in the "Related" links to the side of this question:
Stream android logcat output to an sd card
How to redirect my log output from logcat to the SD-Card on an android device?
...and so on.
Hopefully this helped.
Reading your own logcat messages is covered by other questions.
how can i access logcat file on device
Read logcat programmatically within application
In order to do this when your app crashes you need to install an defaultUncaughtExceptionHandler.
Either on your activity on create or your application on create. Add the following code.
final Thread.UncaughtExceptionHandler oldUncaughtExceptionHandler = Thread.getDefaultUncaughtExceptionHandler();
Thread.setDefaultUncaughtExceptionHandler(new Thread.UncaughtExceptionHandler() {
#Override
public void uncaughtException(Thread thread, Throwable throwable) {
// DO your error handling here.
// Write your log cat, or write your exception stack trace here.
// Get rid of this line if you don't want a popup letting you know that your app has crashed.
oldUncaughtExceptionHandler.uncaughtException(thread,throwable);
}
});
I have an android application that I have recently finished. So I have successfully finished each function and ensured that no errors are encountered.
When I have exported it to an apk file. It runs smoothly. It uses httpRequests to communicate with a remote mySQL server. But there are times that it spontaneously crashes?
For example, I have an activity that would receive input from the user then communicate with the server. It runs smoothly and quickly. But on next run it would crash. And when I restart the application it would run smoothly again even on the second run. I'm just going crazy from this. Are there any explanations for these?
Use ACRA to collect crash reports from your app. You don't need your own server, just a Google Docs form. The integration is described here:
https://github.com/ACRA/acra/wiki/BasicSetup#wiki-Setting-up_your_project
The advantage of using a crash report tool vs. logcat is that you don't need physical access to the device. There are also chances that you see crashes that you or your testers didn't even notice.
The first step to debugging your problem is to get a stack trace. If you can reproduce this on your own device, then right after you see a crash, connect it to your dev pc and run this command:
adb logcat > crash.log
Open the log file, copy and paste its contents on http://pastebin.com/ or similar and add the link to your question. Once we have that, we can try to figure out what's going on.
Can you help me understand how I should debug this errors? What information would you get from this stack trace that might help you understand what is wrong with this code?
I assume andy_lockscreen is not my concern as it doesn't have anything to do with my app.
However what is the meaning of the errors with tag TiApplication and TiHttpClient?
How can I filter to see only errors and traces regarding my app?
I am developing android application using titanium
Thank you,
Ryan
UnkonwnHost means whatever is trying to connect to something online is unable to connect. Either the online content is down (unlikely given that it is google maps) or the device doesn't have a suffecient internet connection, or something else is blocking the connection (iptables perhaps, DroidWall will cause this type of error if you havn't white listed the application attempting to connect)
You can make a filter by clicking the Green "+" that is in the pane just off to the left of the screenshot you provided. Type in the Tag that you are using when you make Log statements within your app. That will narrow down the list to only Logs coming from your application.