Create Hangout on Air - Error Listing Channel Info

[srish]

Karen is redirected to a blank page after clicking create hangout on air button which displays, "Error listing channel info". Any idea what might be the issue here?

[yourcelf]

This error comes up when, during the process of creating a Hangout-on-air, the request for OAuth-authorized data listing the user's YouTube channels fails for some reason. The full error message that Google returned to us is:

{ errors: 
   [ { domain: 'global',
       reason: 'authError',
       message: 'Invalid Credentials',
       locationType: 'header',
       location: 'Authorization' } ],
  code: 401,
  message: 'Invalid Credentials' }

The process is working fine on my end -- is there something different about Karen's google account? Is it an apps-for-domains account or something else like that?

[yourcelf]

Also: is Karen currently signed in to Google?

[srish]

@yourcelf hey, she was logged in with the same credentials that we gave her for accessing the admin panel for this test event page http://unhangout.media.mit.edu/event/25. Yup, it seems to be an apps-for-domains account.

[yourcelf]

Apps-for-domains accounts give us all kinds of problems -- and I guess among the problems they have is that they forbid listing youtube channels. I don't know if they can create hangouts-on-air at all. Can you ask Karen to try this: go to https://www.youtube.com/upload and click "Broadcast" under "Google+ Hangouts on Air"? Is she able to create one that way?

[srish]

Alright! Sent her an email with this information.

[srish]

During the call with NWP folks last Friday, I am assuming that most of the organizers were using the apps-for-domains account (as their accounts end with a custom domain name) and recalling "Karen's case", I was worrying that they will also have troubles while creating/ joining HOA, but surprisingly, it worked decently well for them. Is there a way to identify an apps-for-domains account and how is Karen's account different from theirs?

[drewww]

The problem with apps for domains is that each domain can have its own
fine-grained access settings. If it was all NWP people on the call, I
suspect their domain is configured pretty permissively because we've worked
with them in the past and they're all up on hangouts. I thiiiink that the
default setting for any new domain is to have hangout-related features
turned off, which is why we have troubles so frequently.

I never did any research on whether you can detect those permissions
pre-emptively and provide some user-facing messages that are more
descriptive. It seems like it should be possible, but may be that the only
thing to do is try to use a feature (like join a hangout) and then watch it
fail. Not really sure.

On Mon, Apr 28, 2014 at 11:50 AM, SrishAkaTux [email protected]:

During the call with NWP folks last Friday, I am assuming that most of the
organizers were using the apps-for-domains account (as their accounts end
with a custom domain name) and recalling "Karen's case", I was worrying
that they will also have troubles while creating/ joining HOA, but
surprisingly, it worked decently well for them. Is there a way to identify
an apps-for-domains account and how is Karen's account different from
theirs?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/320#issuecomment-41575354
.

[yourcelf]

Not sure if this is a G+ access issue -- the error here is coming from a call that's trying to list data using the Youtube API, not G+. So at least, this isn't the same as #242 where the issue was
restricting Google+ to members of your own domain. I also don't think it's disabling Hangouts-on-Air entirely that's the issue yet, as the error hit here -- before any attempt to create an HoA.

It could be that a domain setting disabling G+ APIs is bleeding over to YouTube listings, especially now that Google is kindof sloppily integrating the Youtube/G+. It also could be that Karen refused an OAuth permission request at some point (I don't know if/how long that would be cached).

We're totally stabbing in the dark on this one -- it'd be really helpful for us to get direct access to some apps-for-domains accounts with which to test this stuff. Without that, we're stuck asking folks like Karen to walk us through whatever settings their domain might have.

One other thing to check: asking Karen to sign out and in again to Unhangout. We cache people's Google authentication; it's possible that someone could sign out of Google but remain signed in to Unhangout. If something changed about the Google acct since Karen last signed in to Unhangout there could be some authorization sync issue.

[drewww]

I have apps for domains accounts. I'll go spelunking and see if I can find YT specific settings with the aim to recreate that error message.

on mobile - 401.524.3271

On Apr 28, 2014, at 12:25, Charlie DeTar [email protected] wrote:

Not sure if this is a G+ access issue -- the error here is coming from a call that's trying to list data using the Youtube API, not G+. So at least, this isn't the same as #242 where the issue was
restricting Google+ to members of your own domain. I also don't think it's disabling Hangouts-on-Air entirely that's the issue yet, as the error hit here -- before any attempt to create an HoA.

It could be that a domain setting disabling G+ APIs is bleeding over to YouTube listings, especially now that Google is kindof sloppily integrating the Youtube/G+. It also could be that Karen refused an OAuth permission request at some point (I don't know if/how long that would be cached).

We're totally stabbing in the dark on this one -- it'd be really helpful for us to get direct access to some apps-for-domains accounts with which to test this stuff. Without that, we're stuck asking folks like Karen to walk us through whatever settings their domain might have.

One other thing to check: asking Karen to sign out and in again to Unhangout. We cache people's Google authentication; it's possible that someone could sign out of Google but remain signed in to Unhangout. If something changed about the Google acct since Karen last signed in to Unhangout there could be some authorization sync issue.

—
Reply to this email directly or view it on GitHub.

[yourcelf]

awesome, thanks!

[dalareo]

I am facing this issue with my gmail account. Any solution?