I've downloaded Chrome cast sender and receiver application from GitHub. While running the application I am getting some error on my device as well as sender application. I want to debug the Receiver Application. I've followed all the guidelines mentioned on this link [https://developers.google.com/cast/docs/custom_receiver#debugging ] but unable to even open the debug window using the mentioned URL.
Please suggest me something that I need to check to get it debugged as I am new to chrome cast.
Thanks in advance!
You need to have your own application id (by registering your app in Cast Developer Console). Follow the instructions for registration and in that same page, scroll down to Devices and follow those steps as well. After all of that, give it a bit of time, reboot your chromecast and it should work when your app is running on the chromecast.
Related
I implemented oauth in my search message extension. in local debug I see the sign in link and when clicking on it, it opens the window as well. But when I deploy the code to Azure, I dont even see the sign in link and it says unable to reach the app. Below are the error I saw on console:
FIX
Check the App Id and Secret given in Teams Toolkit. It should be correct. You can get more details in application insight.
Hello guys i'm using xamarin forms
i have a class LocalNotif wish content notification calls
on IOS devices i manage to fetch the device even when the app is destroyed but in Android i don't know how
can any one help please.
Thank you
In order to keep the app running in the background you need to create a service.
A service runs in the background (even after closing the app) and provides info for the application, for example when playing a song in Spotify and it keeps playing even after closing the app, notification from Facebook, etc.
I don't think that it's possible to not enter OnDestroy(), but you can read further about services here.
I'm createing a chromecast app for android. I registered my application on Google Cast SDK Developer Console and used the id from there.
As a test I first entered https://google.com as url for my application. that worked perfectly fine. i then changed this url to a local one http://192.168.0.18:8100. Problem is, it allways opens google on chromecast. so i created a new application, but since i did that, the cast button is not shown anymore.
Is my local url valid for chromecast and maybe does it take some time to accept my changed in cast sdk console?
thanks
I want to make a chromecast application to play videos on the Chrome Device. I've downloaded a sender and receiver application from GITHUB. When I use Default or Styled Media Receiver Application, it's working fine. But I want to make a custom receiver for my application. I can't find any tutorial for that. Are there any steps that I should follow to make the receiver for the chromecast device.
I am following following code of GITHUB
https://github.com/googlecast/CastMediaPlayerStreamingDRM
but its not working for custom reciever.
Thanks in advance!!
Look through our documentations here, there are sections for custom receivers and senders. Then look though the GitHub samples. If after doing those you still have specific coding questions, come back here and ask.
In my Android Sender Application, I would like to display the status of a newly discovered Chromecast device. For e.g if another app lets say Youtube is currently casting to this device, then I would like to put a status as "casting Youtube" next to the device name in my receiver list.
For this, once I discover a media route, I connect to that device. On getting a ConnectionCallbacks.onConnected() event, I try to retrieve the application metadata using Cast.CastApi.getApplicationMetadata(GoogleApiClient). But I'm getting a null value here. When I run my Sender App, I make sure that I'm casting to the same Chromecast receiver from another app like Youtube. So I expect the application metadata to reflect Youtube app details its like appId, name etc. Is there a different way to achieve this?
YouTube is still using the old preview SDK so that might be a factor in seeing null. Please try an app that is using the new SDK and see if that returns more useful data. I know there was a bug which caused that method to return null all the time but I believe that was fixed with the recent play services update.