I'm trying to develop a new application for Chromecast device.
However I can't access to Chromecast Debugger by the URL http://[CHROMECAST-IP]:9222 after I've launched my receiver app in Chrome (OS X 10.10.4 / version 45.0.2454.15 dev (64-bit), but it the same with all version).
I've already rebooted and made factory reset my Chromecast few times. My device is also well registered on Google Cast SDK Developer Console and I'm very sure with the device number (I checked 10 times). My app is also registered with an App Id and I'm on the same WiFi network of Chromecast when I cast with my Chrome sender.
Finally, my firmware version is 32904.
Someone can help me to resolve this problem ? If you need other information, ask me.
Please contact our support for this issue; they can help you debug your issue.
To debug a Chromecast device you need to register the app and the Google Cast device and then go to chrome://inspect.
Detailed instructions are here: https://developers.google.com/cast/docs/debugging
Related
I am trying to create a layout for our teams channel tab app but when running the app locally and inspecting it as a mobile device, teams throws an error that the browser is not supported.
Can anyone point me in the correct direction to develop my app for mobile use or how I can view the mobile app from the VS Code Teams Toolkit debugging tools?
I have tried to run the app in chrome and in MS Edge browsers and use the inspector device emulators in both but get the same error. I have also tried connecting via my local machine's IP /the FE port 53000 and also have had no luck there.
I used directly my mobile device (android) with Teams App installed for debugging teams custom tab (both phone and tablet worked fine). Connect your android device to your laptop/desktop (using USB), and then on the phone:
Enable USB debugging
Enable "Developer Preview" in Teams options
In the desktop chrome, navigate to chrome://inspect/devices and you should see your device there in the list available for inspection/debugging. You could probably also connect using local WIFI (?), but I have not tried that. Also never tried that with Edge, so not sure if it works.
https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/developer-tools#access-devtools-from-an-android-device
It's not possible to debug a Teams tab on iOS using Windows (or Mac). Using Dev Tools, we can debug Teams tab in desktop and Android clients.
Ref Document: https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/developer-tools
I registered the chromecast in chrome developer account but still i am not able to debug any apps. Chromecast is showing up in the developer console, but the inspect button is not visible. I tried debugging my own styled media receiver app.
https://developers.google.com/cast/docs/debugging
You might have to restart your device to ensure it downloads the latests configs for development. Also, it is very easy to get the serial number wrong when you register your device in the Google Cast Developer console, so double check that too.
I enabled debugging over bluetooth on my Moto 360
and enabled Android Wear app on my Nexus4.
Status displays target : disconnected
Forwarding the port from my computer shows the status host will be changed to connected, but the target status remains disconnected.
I toggled debug via the bluetooth switch which had no effect.
My phone is a Nexus 4. Is there a problem with my phone or the Moto 360?
I eventually managed to get it working. The issue seems to be related to having paired your device with an emulator first. Take a look at this post to see how I fixed it: http://melix.github.io/blog/2014/10/android-moto360.html
open the applications settings, search for the Android Wear application, then force stop it
clear its data and cache
Search for Google Play Services
Click on Manage space. Delete all data.
reboot your phone
reset your Moto 360
Pair watch with phone
Following the instructions from android.com https://developer.android.com/training/wearables/apps/bt-debugging.html to setup debugging and it should work now.
Done.
I tried it on a Sony z1.
It succeeded without any problems.
So, maybe it's not supported perfectly in Nexus 4.
If you have the same problem, I suggest using another device.
I fixed without factory reset with these steps
-Force stop android wear application and clear cache
-Disconnect emulator on android wear app
-Forget emulator on android wear app
-Connect your real device via bluetooth
-Open debugging over bluetooth
Make sure that debugging options are also active in android wear device
Run this commands in command window:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
I got the email back from Google and they said they have, but having trouble getting it to show up under devices using some of the example code they provide, but now wondering if maybe I gave them the wrong serial or something and it really hasn't been white-listed.
You can always email them with the developer ID (Should be in the email), app ID, and your serial # to have them check. One thing I learned, though (when experiencing the same thing), was that I forgot to configure my chromecast with the "send this serial # to Google when communicating about updates" flag. If that isn't checked, then your Chromecast can't be notified that it is allowed to communicate with your app id. Also note that the Chromecast Android app had a bug (don't know if today's update fixed it) where setting that flag wouldn't stick, so I had to do it through the desktop app and then reboot the Chromecast and wait a few hours for the next time it pinged Google.
Make sure you have the "Send this Chromecast's serial number when checking for updates" setting enabled using one of the ChromeCast setup apps for your OS or Android. And reboot your ChromeCast device after enabling that setting.
You should be able to open Chrome and enter http://[ip.to.chrome.cast]:9222 in the browser address field. If your cromecast device is whitelisted the page will open.
I've started yesterday afternoon studying WP7, so be patient.
I've just created my first test app, registered as developer on AppHub, connected my phone with Zune, registered my phone in my AppHub profile (I can see it in my devices section) and compiled my app.
When I try to transfer my app into phone (using Application Deployment Tool as described here) I get an error that can be traslated as
Unable to connect to device because it's locked by pin
But my device has not any pin (or I don't know to have one) and it doesn't show anything on screen.
What could/should I do?
UPDATE:
Zune is running: if I try I get the error
I close Zune and run WPConnect: my device is connected but the error is the same
When deploying the app, make sure the phone screen is unlocked.
Additinal info: If you are developing from Desktop PC, sometimes connecting from front USB panel wont work.
You can't deploy while the screen lock is active, so try swiping up the lock screen before deploying.