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.
Related
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 have a bound service in separate process. It crashes occasionally due to the oem native libs on certain phones. I am trying to make the app recover from it.
I would like to silently restart the service and continue the workflow. But it seems the error message is always displayed after the service is crashed. Is there a way to suppress the error? We can handle the unhanded java exception, but not sure how to handle the native crash.
Figured out. Handle the sig works for me.
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.
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
I'm running some tests on an Android app that involves Google Maps API and GPS and I get the following error message in LogCat:
05-20 10:41:10.242: ERROR/MapActivity(425): Couldn't get connection factory client
I already gave the right permissions in the Manifest and already tested some other activities involving maps and they worked just fine. But when I try to do something with GPS, I get this error message.
I've read on some forums that probably there is something wrong with my key, but I don't think that's the question because it already worked just fine many times.
You can safely ignore this message. Everyone gets it. Since this comes from closed-source code, we do not know the origin of the message.