I can't get a basic sender app set up. I've tried the CastHelloText sender example, put in my own AppId and get an error immediately after chrome.cast.requestSession() is called when I select my device from the top-right Google Cast extension button. My receiver is based off of Cast-Simple-Receiver. I've done the whole unplugging power/plugging back in thing to restart ChromeCast, but that doesn't resolve my issue.
Resources out there seem kind of slim at the moment, but is there a place that explains everything in-depth without having to jump from site to site? Also, take a look at the image I've attached. I can't figure out what that other URL is supposed to be.
My specific error from the requestSession() looks like this:
{code: "session_error", description: "NOT_FOUND", details: null}
EDIT: I've verified that I can connect to the default chrome.cast.media.DEFAULT_MEDIA_RECEIVER_APP_ID but my receiver app can't be connected to. I've registered my device and restarted it multiple times. I've now removed it and am trying to re-register it to see if that helps (even though it said it was ready for dev).
Check these; hopefully they get things sorted out:
Make sure you have registered your chromecast device on the developer console. Double check the serial number since sometimes it is hard to read it.
During the chromecast setup, there was a box stating something like "Send the serial number ..", make sure that is checked
Wait 1/2 hour or so and reboot your chromecast
Check whether you can access http://<chromecast-ip>:9222 from a chrome browser on the same wifi network; if you can, then your device is ready for development
As for the area on the image that you have pointed to, that is more for informational purposes at this point
Related
I'm new to cypress and I want to create tests for a rather oldfashioned website which is unfortunatelly not available on the internet.
When I perform a simple call to the website cypress crashes:
cy.visit('http://10.0.0.6:8080/dmc')
The message I get within the chromium instance is: "Whoops, there is no test to run. Choose a test to run from the desktop application."
Shortly before I get this message, I see some messages in red in the left chromium task-runner-pannel (sorry for not knowing the correct term). But the timespan is too short to read it.
So my questions are, any ideas why cypress is crashing? I know this may gonna be a tough one since the website is not accessable.
Can I find these "red-messages" somewhere else? eg a logfile?
BR,
Richard
I have a webapp in production that interacts with Google Drive through Google Drive API.
I need to change some settings in Drive interaction but I can't save.
When I save the Drive UI integration page, I receive this error:
There's a problem at our end.
Please try again. If the problem persists, please let us know using
the "Send feedback" link below. Thanks!
(spying Network console: there is an Internal Server Error in a POST call)
I tried to send feedback for months: nobody answers and the bug is still there.
I tried also to create another project: I can save the first time but then the bug returns.
How can I do? Has someone the same problem?
Is there a way to receive a reply from Google? Is there some workaround?
Thank you.
i think that problem must be Client ID
before adding Client ID, go to the Credentials -> OAuth 2.0 Client IDs
then select edit your Client ID. after that your production site url add to Authorized JavaScript origins and Authorized redirect URIs.
then enter your Client ID in Drive UI integration page
For myself trying to get the Drive UI configured I noticed a couple of errors (that don't have any specific error messages)
When adding in an Open URL it has to be a valid domain, so for instance I tried to test it out with local host, to no avail. However something like https://devbox.app.com worked, but something like https://localhost:8888 does not. Even though https://localhost is a valid javascript origin in the client_id configuration (at least for the app I am working on, not sure about other apps), localhost doesn't work as an open URL.
When adding in the mimeTypes it needs to be in the format */* and can include custom mimeTypes like application/custom+xml and application/custom-name+json not sure for other custom types that are not in a particular format like xml or json. Also not sure about wildcards.
When adding in file extensions do not add in the '.' just the name of the file extension.
The app icon I found only failed to upload the image when the image wasn't the exact dimensions, I actually ended up editing some icons in photoshop to change the pixel x pixel values as a quick work around during dev.
That worked for me to get it to save and I tested it with a file that had a custom mimeType (application/custom-name+xml specifically) and custom file extension!
I am trying to cast videos from my html video player to TV via chromecast.
Sender: CastVideos-chrome
https://github.com/googlecast/CastVideos-chrome
Receiver: CastReferencePlayer (registered as a Custom receiver, hosted on my github,
https://github.com/PhilSSOO/052617_CastReferencePlayer
and the app ID was input to the sender's CastVideos.js file)
The whole sender folder was put to my server applied from Apache. The path is
C:\Apache24\htdocs\CastVideos-chrome
Putting http//localhost/CastVideos-chrome/ to the address bar of the chrome browser and hit Enter, the app is up and running with videos being cast to TV. Now, my question is: How can I know my custom receiver is functioning? I tried to do some modifications on my css file (receiver app consists of player.html, player.js, player.css) but nothing seemed to be changing on my TV screen.
Please help!
Here's what the Custom Receiver Application has to say:
Note: Google Cast receiver applications must be hosted on secure
servers supporting https when published. Publishing a Google Cast
receiver application may take several hours to propagate to all Google
Cast devices (up to 6 hours). If you wish to verify that your
published application is working properly, you can manually restart
your Google Cast device to force a load of new configuration data.
Check the docs for more details about Application Configuration.
noogui,
Thank you for your reply.
I purposely modified the CSS file of my custom receiver (styled the progressBar with green color --- rgb(48, 249, 55) --- ), hosted it on my github account, published the receiver, waited 6 h and started testing. Upon starting my sender app the video got cast to TV, and the progressBar is still yellow, NOT GREEN. This means my receiver is not functioning!
I also tried a style receiver, and even styled the progressBar with a wrong color (rgb(48, 249, $$$)). The sender app also cast the video to TV without any complaint. The conclusion is, my receiver is not being called!
I tried to use the Chrome Remote Debugger to debug, but my chromecast device, although showed up on my laptop, didn't have the inspect link with it, so I couldn't go further.
BTW, my sender works fine with default receiver.
I got lost!
Thanks!
I figured that out. The issue was related to app hosting.
When a custom receiver is registered to google cast console, the receiver hosting URL and associated sender hosting URL are not where they are stored, but where they are published. For example, the receiver hosting URL
https://github.com/USER/REPOSITORYNAME
is not to be used, but the following URL is
https://USER.github.io/REPOSITORYNAME......
(this can be accessed via Settings --- GitHub Pages)
Once the correct URL is used, my custom receiver is up and running!
Cheers!
I have problem with launching Google-Cast application similar to sample CastHelloText-chrome. I slightly modified example code for my specific purposes. The goal for creating this application is to send and show image data directly in Chromecast device.
Particularly the difference between official sample and my code is in message format and its content, sent by sender application. Sender application took png image coded by base64 and send through message bus with custom namespace. Receiver application get this message and use this as data source for html object <img>.
Error appears when I do this steps:
Reload sender page, checking console if any device found.
Send the form by just pushing enter on input box (text is ignored).
Now a popup from Chromecast extension shows. Next there are two scenarios:
3a) I confirm casting to device by choosing one from the list, then I get this error message in console:
onError: {"code":"channel_error","description":"Error: Timeout","details":null}
3b) I just click somewhere else, I get this error:
onError: {"code":"cancel","description":"User closed popup menu","details":null}
Both of errors are caused by calling function chrome.cast.requestSession in chromehellotext.html at line 161, but what's really wrong I don't know.
When I step sender script I realize that function sessionListener is never called. I know that something go wrong when code try to call chrome.cast.requestSession, where described error raises. So I need help if I missed about right way to use Google-Cast API or If this problem has something to do with networking issues.
Receiver application is registered on Google Cast SDK Developer Console and I'm testing on registered device with some serial number. I'm using Google Chrome in version 42.0.2300.2 canary (64-bit) and Chrome version 40.0.2214.111 (current stable I suppose). For testing I also tried to turn off Windows Firewall entirely but with no luck.
Edit:
There were some syntactic errors that caused error message described above.
It seems like you are trying to use the data/control channel to send an image; please don't do that; that channel is not meant to be used for large data communications; in fact it cannot send anything which approaches or exceeds 64k. If your goal is to send images from your local machine, you would need to run a local web server on your local machine and serve images through the web server.
For and easiest tutorial you can have a look to this tutorial.
It is well explained in this tutorial.
Chromecast Sender application
There is no need to maintain session by yourself.
just add button and enjoy casting
mCastManager.addMediaRouterButton(mediaRoutebtn);
I found a source of my problem. There was something wrong in receiver code - syntactic and runtime errors, so I must admit that my code wasn't functional. Now its working in terms of launching application and getting session.
Unfortunate thing is that the error message generated by Chromecast extension didn't match the actual error - at least it was a bit confusing when I didn't know what's really happening on receiver side without ability to debug the code.
I decided to try out Firebase hosting and wanted to start fresh so I deleted my one and only app, but when I tried to create a new app with the same name I was unable to due to the error:
"This Firebase URL is not available"
I can only guess this is because of caching of app names/URLs? Hopefully it will become available (unless someone else beats me to it) after some timeout? Any info from others who have experience with this issue or otherwise know the answer is appreciated!
Not sure whether this is the right place to ask although Firebase suggest coming to SO because they apparently monitor Firebase-related questions closely according to their website.
Thanks!
Once you delete a Firebase URL, it is permanently unavailable. It cannot be recovered.
During confirmation, you should see a message like this, which explains in detail:
This stems from a number of abuse vectors that are possible by misappropriating a project id that the prior owner believes is deleted and could still have apps/releases in the wild attached to the defunct backend. Since compliance requires that we purge all data related to the project, including information about ownership, there's not even a way to restore one you personally deleted.