android - Does Chromecast MediaRouteButton have a production bug? -
* -- issue app id not waste anybody's time.
on off chance helps other noob real problem forgot check the:
"send serial device # google when checking updates" checkbox below fold on chromecast device setup application.
i had reboot chromecast device take effect.
now naddaf's github works fine!
before beginning: have no problem casting examples use actionbaractivity chromecast configuration not issue.
in reference to:
https://github.com/googlecast/mediarouter-cast-button-android
there seems bug in
mmediarouter.addcallback(mmediarouteselector, mmediaroutercallback, mediarouter.callback_flag_request_discovery);
located in: mediarouterbuttonactivity.java
never receives callback.
this reported 4 days ago:
https://github.com/googlecast/mediarouter-cast-button-android/issues/5
the long version:
i have mature beta of video based android app uses fragmentactivity , targets sdk 14+.
i have set chromecast device development , works sample apps in sdk/extras fine. problem there predicated on inheriting actionbaractivity mutually exclusive/incompatible fragmentactivity.
every example stackoverflow or github (only 1 project) have tried uses android.support.v7.app.mediaroutebutton run mediaroutebutton never instantiates.
when tracing see following issue:
mmediarouter.addcallback(mmediarouteselector, mmediaroutercallback, mediarouter.callback_flag_request_discovery);
the callback added chromecast sdk never calls it.
google gives entire walkthru using actionbaractivity makes fleeting reference alternative use of mediaroutebutton.
i have wasted 2 days trying wrap head around guessing one's way through sub-optimal.
is there has working example of using mediaroutebutton fragmentactivity or link working documentation. seeming major oversight chromecast team.
thanks!
Comments
Post a Comment