Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ClassException: Channel.isAppAvailable (Channel.java:472) #128

Open
grolschie opened this issue Apr 27, 2020 · 6 comments
Open

ClassException: Channel.isAppAvailable (Channel.java:472) #128

grolschie opened this issue Apr 27, 2020 · 6 comments
Labels
bug A confirmed issue with the library

Comments

@grolschie
Copy link

grolschie commented Apr 27, 2020

Hi. I've been using your library for quite a while now with very little issue. However, I notice one of my users had this error in Android's error reporting:

java.lang.ClassCastException: 
  at su.litvak.chromecast.api.v2.Channel.isAppAvailable (Channel.java:472)
  at su.litvak.chromecast.api.v2.ChromeCast.isAppAvailable (ChromeCast.java:237)
  at [appname].CastFragment.handlerTask (CastFragment.java:706)
  at [appname].CastFragment.access$2500 (CastFragment.java:53)
  at [appname].CastFragment$16.run (CastFragment.java:602)
  at java.lang.Thread.run (Thread.java:818)

I wasn't sure if I should report it or not as I wouldn't have any idea on how to replicate this. Using library version: 0.11.2.

@vitalidze
Copy link
Owner

It seems that for some reason chromecast device sends something different than "GET_APP_AVAILABILITY" response for the request. To figure out what happens please send the log file with "DEBUG" level messages to see the exact request/response.

@vitalidze vitalidze added the bug A confirmed issue with the library label Apr 28, 2020
@grolschie
Copy link
Author

Hi. I am unable to replicate this because the above is all that appeared in the anonymized log in Android Vitals. The Chromecast device is the built-in Chromecast Audio (1.21.76349) on a Sony STR-DN1080 AV receiver.

I thought I'd post this anyway, just in case it was useful - but feel free to close this bug report.

@vitalidze
Copy link
Owner

It is definitely useful. But still, is there a way to somehow enable the debugging messages for that particular Android app? Or this will flood your logs?

@grolschie
Copy link
Author

Hi. Unfortunately developers are meant to disable logging and debugging before publishing to Google Play. The snippet I posted is all that was shown me in the Google Play developer's console, but often I get more info than that. Fortunately (or unfortunately for this report), I have only seen this error the one time.

@grolschie
Copy link
Author

I haven't seen this exception in Android Vitals since.

@grolschie
Copy link
Author

Update: over a year later and I haven't seen it since.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A confirmed issue with the library
Projects
None yet
Development

No branches or pull requests

2 participants