Not receiving channel id while using Guestbook samples. about chrome-extensions-samples HOT 8 CLOSED

Is the user logged in? The normal way that getChannelId fails is if the
user is not logged in to chrome.

On Sun, Aug 18, 2013 at 2:50 PM, H1ccup [email protected] wrote:

This is what I get in the console:

pushMessaging.getChannelId: 1
at Guestbook.initialize
(chrome-extension://pclhfkljokicifohhjodckkdjfagcjei/Guestbook.js:75:24)
at chrome-extension://pclhfkljokicifohhjodckkdjfagcjei/background.js:10:11
lastError:29
set

I'm not sure what exactly it means. Any help? I'm using your sample but
not being able to come up with a solution to get the channel id.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/127
.

from chrome-extensions-samples.

Yes, the user is logged in. Retried it again. Got the same error + this:

Guestbook: starting to listen Guestbook.js:39
pushMessaging.getChannelId: 1
at Guestbook.initialize (chrome-extension://pclhfkljokicifohhjodckkdjfagcjei/Guestbook.js:75:24)
at chrome-extension://pclhfkljokicifohhjodckkdjfagcjei/background.js:10:11 lastError:29
Guestbook: Channel ID not found. Eek! Guestbook.js:39
Guestbook: Got Message
Object
Guestbook.js:37
Guestbook: Got Message
Object
Guestbook.js:37
Guestbook: Got Message
Object
Guestbook.js:37
Guestbook: Got Message
Object
Guestbook.js:37
Application launched. Guestbook.js:318

Went through the code, which suggests that the user isn't receiving the channel Id, but is waiting for a message from the GCM.

from chrome-extensions-samples.

Just to add to this, I'm using Chromium and not Chrome, on a Ubuntu. Not sure if that should make much of a difference.

from chrome-extensions-samples.

This should work on chromium on Ubuntu, as long as you are signed in to
chrome sync.
I'll see if I can reproduce your problem, in chromium, using Ubuntu.

On Mon, Aug 19, 2013 at 9:30 AM, H1ccup [email protected] wrote:

Just to add to this, I'm using Chromium and not Chrome, on a Ubuntu. Not
sure if that should make much of a difference.

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

from chrome-extensions-samples.

Thanks! It would be nice if you checked it out. I've also signed out of chrome sync and signed back in, deleted the extension and reloaded it, but ended up getting the first error all over again. No channel id.

from chrome-extensions-samples.

FYI - I am still investigating why you might not be getting the channelId.
I think I can repro the problem now even without the push guestbook app,
and others have reported a similar problem. It may take several days of
invetigation before I know the cause, and there are competing priorities,
so I'll let you know as soon as I find out.

On Mon, Aug 19, 2013 at 10:44 AM, H1ccup [email protected] wrote:

Thanks! It would be nice if you checked it out. I've also signed out of
chrome sync and signed back in, deleted the extension and reloaded it, but
ended up getting the first error all over again. No channel id.

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

from chrome-extensions-samples.

I've investigated, and I found two most likely potential causes.
The first one can happen if you are running a developer build of chromium instead of a retail build of chrome.

The second one is that there is a bug in chrome itself (it is being investigated actively) where you sometimes get signed out, but it looks like you are still signed in to chrome. It should be signed back in properly if you completely shut down chrome and re-start it. You can click on the chrome menu, and check to see if it says "Signed in as [email protected]", or Error signing in. To completely shutdown chromium on Ubuntu, type "killall chromium" on the command line, then use "ps aux | grep chromium" to make sure there are no instances left running.

from chrome-extensions-samples.

Closing. If the problem is still happening, please report a bug at http://crbug.com/new

from chrome-extensions-samples.