I still cannot get my chromecast into developer mode. I tried compiling the sample android app and my chromecast doesn't appear in the list of devices. I have indeed checked "Send this Chromecast's serial number when checking for updates" and rebooted my device. I even let it sit overnight to give it time to contact Google. When i got to http://[my chromecast ip]:9222 I get connection refused. I can ping it though. And http://[my chromecast ip]:8008/apps/ returns an XML response.
When I first sent the request to Google, they said the whitelist was backlogged but shortly thereafter they said the backlog was cleared.
Any ideas besides the fact that maybe whitelisting didn't work on Google's backend?
Even I had same problem earlier
In earlier version of chrome-cast app (for android) there was an issue Send this Chromecast's serial number when checking for updates is uncheking always, So I removed that app and again installed new version. That bug was removed now. OPtion is by default Checked.
If it doesn't work then try to use other device. Surely that will solve your problem
Related
I have never deployed an app for texting in a real iOS device, only on an iPhone 7 plus simulator. I've watched some tutorials on how to do it and this is what I have done so far.
I have made an iOS Development Certificate. I made an App id, connected a device and entered the UDID. Then created a new device and at last I have made a Provisioning Profile with the iPhone 7 Device connected. The iOS development certificate connected and the App ID connected. After I did all of that, I continued to watch all the tutorials but there seems to be a change which I can't figure out.
As you can see, in the picture above there is a view detail button which you click then download your Provisioning Profile to your XCode, but for me there is no View Detail button. Instead it looks something like this.
So unfortunately, I don't know what to do from here. I tried going to Xcode > Window > Devices then right clicked on my device then it looks something like this.
So I click Show Provisioning Profiles, press "add" then add my Provisioning Profile. The next thing I did was go back to Xamarian went to info.plist, double clicked it and then entered my Bundle Identifier.
Then right clicked the 2 Calculator file, went down to Options and then set everything up, as you could see in the picture. Then I press run but it doesn't seem to work
This error message comes up:
I am pretty sure I have done everything right, but there seems to still be an error. The only possible bit I think may have gone wrong is when there wasn't the "view detail" button, so I did it a another way. Maybe the problem is I downloaded the Provisioning Profile on the iOS Device, but not in the Xcode mac or something?
I don't have a clue what I did wrong and have tried everything about 5 times but it still didn't work. It will be great if someone could help.
These are all the Certificate and stuff I did in the App development section.
Not enough reputation to comment, so I am going to take a shot in the dark here. My question to you is, did you download the certificate to your MacBook before or after you added your mobile device to it? Your Mac has to know of which devices you have allowed to develop on, so you need to make sure your .mobileprovision on your Mac has that UDID in it.
You can check if your .mobileprovision is added by looking in "~/Library/MobileDevice/Provisioning Profiles" and sorting by "Date Modified" to see if you have a fresh one updating after you downloaded it from developer.apple.com. Xcode will assign a GUID to the name so the provisioning profile will not have the name displaying on the website.
Also, the error possibly looks certificate related. Is the certificate valid and trusted in your keychain? I noticed no mention of adding the certificate to the "Keychain Access" application.
Link to previous issue: Gmail contextual gadget broken
Yesterday we received a couple of customer complaints regarding our Gmail gadget. They claimed that it had gone missing from their account. This morning, several of our employees have reported the same although, this isn't happening for everyone.
We haven't made any changes to the gadget and since it loads for some, I don't think this was caused by us.
What happens:
The window of the contextual gadget does not appear in the main Gmail interface
The window of the contextual gadget does not appear when opening an email in a new window (shift + click). This differs from when this happened previously.
We've also contacted Google and they have responded that they are looking into the issue. We've also seen that the shift-click to open an email in a new window doesn't work as a work around this time.
The last time this happened our monitoring showed that about 10% of users lost their access to the gadget per-day. We seeing a similar drop off in activity this time around.
Here are the details of the response I received from Google for this issue
Thank you for contacting Google for Work Support. I understand that
that you Gmail Contextual Gadgets have disappeared again from the
Gmail web interface.
I notice there are other user reporting a similar behavior hence he
have requested an update from our Eng team and I am currently waiting
for their response. As soon as I have an official response, I will be
contacting you back directly with the next steps.
Also I notice you mentioned that the previous workaround is no longer
working. Previously the workaround provided was to press "Shift" and
then click on the email. The email will be opened in a new window and
then the gadgets should be displayed. Can you please confirm if the
above workaround is working or not?
I’ll keep this case open while I wait for your reply. If you have any
other questions or additional comments, don’t hesitate to reply and
I'll be happy to continue helping you.
Sincerely,
Wilmer Google for Work Support
Here is the latest update from Google
As before this issue appears to be UI based as opposed to any problem with the Contextual Gadget API itself, we've gathered some troubleshooting information from affected test environments and are working on identifying a clear root cause and then remedying the behaviour at the moment.
There isn't any further you need to do on your end, I'll update you as I learn of any changes in the status of this behaviour.
Regards,
Patrick
I added my Chromecast device on the "Google Cast SDK Developer Console" and it's showing as "Ready For Testing" on the console. Unfortunately, my device isn't showing as available when I'm launching from an un-published app.
Additionally, the remote debugger isn't loading at http://[ip]:9222
Any clue on how to resolve? I've tried removing/adding the device again and rebooting it a few times.
Make sure you have entered the correct serial number (take a photo and enlarge it since it is easy to read it incorrectly) in the dev console. Also reboot your chromecast to read the config again. If it still doesn't work, contact our help center for further assistance.
I recently purchased a LG Music Flow H3 to test my Google Cast app with an 'audio-only' device. I've enabled audio-only device support within the Google Cast Dashboard and I've registered the device for development. My app works as expected when played to Google Chromecasts, however when attempting to load the receiver app on the LG device I get the following error:
{"reason":"NOT_FOUND","requestId":1,"type":"LAUNCH_ERROR"}
Thinking that perhaps 3rd-party devices can't be registered for development, I went ahead and published my app. Unfortunately this did not address the problem.
Upon further investigation, I'm noticing that other Google Cast apps (i.e. Songza, TuneIn, Pandora, etc. on both Android & iOS) aren't able to play to the LG Music Flow H3 either.
I discovered that the only way to get the H3 to play from Google Cast apps (both my app and others) is to first run the LG Music Flow multi-room audio app. Running the LG Music Flow app appears to effect the device's _googlecast._tcp zeroconf service discoverability. And sometimes the H3 shows up in zeroconf yet you still can't play to the speaker unless the LG Music Flow app is running.
This seams like very strange behavior. I called LG Tech Support, and they recommended I return the device and exchange it for a different one. I did this, and I still get the same result.
Is this how Google Cast on 3rd-Party devices is intended to work? Have I encountered a buggy 3rd-party implementation?
This is not the intended behavior for sure. You are supposed to be able to launch your 3rd party application on the speaker.
And it works for me.
The fact you are not able to use any other 3rd party apps (TuneIn, Pandora etc) indicate this is a some general problem and not specifically with your app.
Couple of steps I would try:
- Setup you H3 speaker on Wifi (vs Ethernet) and get the latest SW version using the Music Flow app.
Have you Factory reset the device? if you did, you will need to go through setup again. I have noticed Google Cast becomes enabled only after first complete setup.
Please try rebooting, and than try casting apps like TuneIn or Pandora and than see if this works (without using the MusicFlow app). I have noticed in the past that if some app is loaded and is behaving badly (for example uses tons of memory) it will put the speaker into a bad state that don't allow any app to work until reboot. So perhaps when you are casting your app, it gets into a bad state causing other apps to fail afterwards.
Have you made sure not to consume to much memory? avoid graphics or video?
I have a SharePoint instance serving as our Extranet to our salesforce - communicating over HTTPS. All sales agents have a Blackberry device, but none can access our Extranet.
In IIS, we only have ASP.NET Impersonation and Windows Authentication enabled, but the BB device doesnt even prompt for credentials, it just receives a 401 error.
Needless to say, the site is browsable on other devices (PC, tablet, iPhone..), so it seems to be something specific to BB settings - or thats my inclination. Anyone have any thoughts on how I can troubleshoot\resolve?
I should add.. I downloaded the BlackBerry emulator for my PC, and that too has the same issue, so I dont think it's a BlackBerry service setting.. but something with how the device is attempting to connect\authenticate.
OK, found the answer (apparently the Google machine is running much better today than it was yesterday ;)
Blackberry doesnt support Windows Authentication since the browser is too old. I had to turn on Basic Authentication, which isnt recommended unless your running over SSL.. which fortunately I am. Found the answer here: http://support.microsoft.com/kb/907273